Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: bump pg_graphql version #1455

Merged
merged 3 commits into from
Feb 21, 2025
Merged

Conversation

staaldraad
Copy link
Contributor

@staaldraad staaldraad commented Feb 20, 2025

What kind of change does this PR introduce?

  • upgrade pg_graphql v1.5.1 to v1.5.11

Additional context

Depends on version v1.5.11 being tagged and released

Action Items

  • New extension releases were Checked for any breaking changes
  • Extensions compatibility Checked
  • Backup and Restore Checked
    • Proceed to backup testing while extensions are enabled
      • After every restore, re-run the tests specified at point 3.1

Extensions compatibility testing

  1. Enable every extension
    1. Check Postgres’ log output for any error messages while doing so
      1. This might unearth incompatibilities due to unsupported internal functions, missing libraries, or missing permissions
  2. Disable every extension
    1. Check Postgres’ log output for any cleanup-related error messages
  3. Re-enable each extension
    1. Run basic tests against the features they offer, e.g.:
      1. pg_net - execute HTTP requests
      2. pg_graphql - execute queries and mutations
      3. …to be filled in

Backup Testing

Follow the testing steps steps for all the following cases:

  • Pause on new Postgres version, restore on new Postgres version
  • Pause on older Postgres version, restore on new Postgres version
  • Run a single-file backup backup, restore the backup

Testing steps

  1. Generate dummy data
    • the ‘Countries’ or ‘Slack clone’ SQL editor snippets are decent datasets to work with, albeit limited
  2. Save a db stats snapshot file
    • Do this by running supa db-stats gather -p <project_ref>
  3. Backup the database, through pausing the project, or otherwise
  4. Restore the backup, through unpausing the project or cli
  5. Check the data has been recovered successfully
    1. Visual checks/navigating through the tables works
    2. Run supa db-stats verify against the project and the previously saved file

@supabase supabase deleted a comment from linear bot Feb 20, 2025
@staaldraad staaldraad force-pushed the etienne/sec-205-pg_graphql branch from ee3d3f1 to 5bf5b63 Compare February 20, 2025 16:34
@staaldraad staaldraad marked this pull request as ready for review February 21, 2025 06:57
@staaldraad staaldraad requested a review from a team as a code owner February 21, 2025 06:57
@staaldraad staaldraad force-pushed the etienne/sec-205-pg_graphql branch from dd416be to 4eb4bb1 Compare February 21, 2025 06:59
@staaldraad staaldraad force-pushed the etienne/sec-205-pg_graphql branch from 4eb4bb1 to 0952290 Compare February 21, 2025 07:00
@staaldraad staaldraad merged commit 32ccff5 into develop Feb 21, 2025
11 checks passed
@staaldraad staaldraad deleted the etienne/sec-205-pg_graphql branch February 21, 2025 09:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants