Skip to content

feat: pg_cron 1.6.2 #900

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

Merged
merged 1 commit into from
Mar 11, 2024
Merged

feat: pg_cron 1.6.2 #900

merged 1 commit into from
Mar 11, 2024

Conversation

soedirgo
Copy link
Member

@soedirgo soedirgo commented Mar 7, 2024

What kind of change does this PR introduce?

  • upgrade pg_cron from v1.4.2 to v1.6.2

Additional context

An upgrade to v1.5 was reverted because of a breaking change, but the breaking change is handled in #899

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

@soedirgo soedirgo marked this pull request as ready for review March 7, 2024 09:25
@soedirgo soedirgo requested review from a team as code owners March 7, 2024 09:25
@mkmoisen
Copy link

The newer versions of pg_cron with sub-minute scheduling will be so helpful.

@soedirgo soedirgo merged commit 8e336d2 into develop Mar 11, 2024
@soedirgo soedirgo deleted the feat/pg-cron-1.6.2 branch March 11, 2024 07:09
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