Repository navigation
Post: PostgreSQL 19 Is Out: What to Check Before You Upgrade - #2249
Merged
Merged
Conversation
Deploying devops-daily with
|
| Latest commit: |
d27158f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6413464c.devops-daily.pages.dev |
| Branch Preview URL: | https://content-postgresql-19-ga.devops-daily.pages.dev |
Upgrade guide for the 19 GA: pg_upgrade blockers, settings that stop the server from starting, changed defaults and results, monitoring renames, and a pg_upgrade and logical replication path, with check queries for 18. Links back from the delay post and the Introduction to PostgreSQL guide.
Smoke test on 18.7 and 19.0: per-role removed settings pass pg_upgrade --check but fail the real run, --check stops at the first failed check, dutch_porter needs its own configuration, postgres_fdw READ ONLY example, JIT hashing fix after 19.0.
bobbyonmagic
force-pushed
the
content/postgresql-19-ga
branch
from
November 19, 2026 11:39
380b0c1 to
b81a375
Compare
bobbyonmagic
marked this pull request as ready for review
November 19, 2026 11:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New post for the PostgreSQL 19 GA: an upgrade guide for people who run Postgres. It covers what blocks
pg_upgrade, what stops a 19 server from starting, changed defaults, changed results, monitoring renames, and a short upgrade path (pg_upgrade and logical replication). Every change links to the release notes, the docs/19 pages or the commit.postgresql-19-upgrade-checklist, publishedAt 2026-11-19T15:00:00ZREL_19_0tag (5c839a2a08). Release notes andguc_parameters.datare identical to7f40ddf3cf, the commit the first draft used.REL_19_0on a throwaway droplet: every check query,pg_upgrade --checkand--link, post-upgrade steps, config and login checks, logical replication cutover.escape_string_warningpassespg_upgrade --checkbut fails the real run;--checkstops at the first failed check;dutch_porterneeds its own configuration; a real postgres_fdw READ ONLY example; a note on the JIT hashing fix that landed after 19.0.scripts/generate-content-og.ts.