Upgrading¶

When a new version of pg_relay_notifier is released, a managed-cloud deployment is upgraded by applying the updated managed SQL file. Because the schema was deployed manually rather than via CREATE EXTENSION, there is no ALTER EXTENSION command to run.

make managed
psql "$YOUR_DB_URL" -v ON_ERROR_STOP=1 -f install/pg_relay_notifier--managed--1.0.sql

Each release's notes describe exactly what changed. Where a release ships a genuine upgrade delta (rather than the base install script being idempotent-safe to re-run), apply the version-specific upgrade file that release provides rather than re-running the full base install against an existing deployment — check the release notes for which applies.

Verify after upgrading¶

SELECT latest_version FROM pgrelay.list_applications()
WHERE lower(application_name) = 'pg_relay_notifier';

SELECT * FROM pgrelay.preflight() WHERE check_name LIKE 'notifier:%';   -- all 'ok'

No pg_relay Processor restart is needed — request_reload() (run automatically at the end of the install/upgrade script) makes every running Processor instance re-read the application registry and re-run preflight within about a second.

Upgrading the UTL_MAIL Compatibility extension¶

If pg_relay_notifier_utl_mail is also installed, upgrade it the same way, after upgrading pg_relay_notifier itself — see that book's own installation page.