Skip to content

Conversation

samrose
Copy link
Collaborator

@samrose samrose commented Feb 20, 2025

What kind of change does this PR introduce?

  • upgrade extension from v0.0.0 to v0.0.0

Additional context

Add any other context or screenshots.

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

@samrose samrose requested a review from a team as a code owner February 20, 2025 19:38
Copy link

linear bot commented Feb 20, 2025

@samrose samrose merged commit c4b657b into etienne/sec-205-pg_graphql Feb 20, 2025
10 of 11 checks passed
@samrose samrose deleted the sam/sec-205-pg_graphql branch February 20, 2025 20:27
@staaldraad staaldraad mentioned this pull request Feb 21, 2025
3 tasks
staaldraad added a commit that referenced this pull request Feb 21, 2025
* chore: bump pg_graphql version

* chore: update our nix pkg for pg_graphql too (#1458)

* chore: bump version

---------

Co-authored-by: samrose <[email protected]>
damonrand pushed a commit to cepro/postgres that referenced this pull request Jun 15, 2025
* chore: bump pg_graphql version

* chore: update our nix pkg for pg_graphql too (supabase#1458)

* chore: bump version

---------

Co-authored-by: samrose <[email protected]>
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.

1 participant