- REPACK CONCURRENTLY to reclaim disk space, which also affects performance.
- Logical replication of sequences - Fantastic addition. This is a missing piece in the major-version upgrade story which required extra scripting, and enable additional usecases.
- WAIT FOR LSN is a game-changer for read-replicas. For read-after-write, where the write goes to the master and the read hits a random replica. And also read-after-read, where each read may hit different replicas.
Add to that additional performance improvement and the plan advice extension, this makes 19 one of the most exciting releases of PostgreSQL.
Copy-and-patch is going to generate worse code than the LLVM-based JIT, all things being equal. You'll get shorter compile times, but in my experience, that's only really a part of the JIT's problems. TBH it's a bit sad that they turned on the JIT in the current state to begin with; it clearly wasn't ready, and perhaps needed a couple more rounds with the design.
Out of curiosity, are there any copy-and-patch JITs that are clear-cut successes? (Python's JIT is the most high-profile case, and it's definitely not one.)
I always wondered why sequence numbers weren't replicated, it added another step to the stress of upgrading via pg_backup but thanks for adding it to PG19!
Personally I would say, for critical production systems, its still good to wait for the .1 release.
Part of why delaying is helpful is that more people will actually install the release than they do during the beta/RC cycle, and (in my read) most of the delay of the release was not necessarily because of significant bugfixing of features that remained in 19 (though e.g. REPACK certainly had its fair share of fixes), but rather the Postgres committers being overly busy with some of the security fixes that just went into 18.7 and the other minors, combined with some late removals of features that warranted an extra beta and RC release.
> Part of why delaying is helpful is that more people will actually install the release than they do during the beta/RC cycle
Unless everybody starts waiting for .1 :)
> was not necessarily because of significant bugfixing in 19
They discovered some serious bugs in new features which weren't really solvable in a way the devs were comfortable with (with regards to long-term maintainability and stability). So some of the new features were rolled back and that process also took some time.
Yep, agreed its bad if everyone does it - but e.g. you could upgrade pre-prod / staging and only do prod once the 19.1 release is out.
To clarify what I meant with the second part: If you look at e.g. SQL/PGQ it was reverted pretty late (beta4), but that revert doesn't mean that other features don't have bugs that are yet to be ironed out. e.g. just this morning a bugfix went in that can crash EXPLAIN (BUFFERS) (without ANALYZE) when you have auto_explain turned on [0]. Edge case, but could happen, and the fix will only be in 19.1 in February 2027.
It really depends on your use-case.
Personal use database and you have regular backups, can tolerate some bumps - probably fine to test drive it, but keep an eye open.
Serious production system - let it "soak", as they say these days. My personal rule of thumb is 6 months for major versions, it has proven itself many times over many different technologies.
Amazing release, really exciting features:
- REPACK CONCURRENTLY to reclaim disk space, which also affects performance.
- Logical replication of sequences - Fantastic addition. This is a missing piece in the major-version upgrade story which required extra scripting, and enable additional usecases.
- WAIT FOR LSN is a game-changer for read-replicas. For read-after-write, where the write goes to the master and the read hits a random replica. And also read-after-read, where each read may hit different replicas.
Add to that additional performance improvement and the plan advice extension, this makes 19 one of the most exciting releases of PostgreSQL.
Big big big kudos to the contributors, thank you!
> Change JIT to be disabled by default (Jelte Fennema-Nio)
That was long overdue. The performance impact on perfectly fine tuned queries was horrendous.
It's also disabled by most OSM apps that make heavy use of PostGIS for exactly that reason.
Maybe it wouldn't be that bad if a copy-and-patch kind of JIT would be used?
Copy-and-patch is going to generate worse code than the LLVM-based JIT, all things being equal. You'll get shorter compile times, but in my experience, that's only really a part of the JIT's problems. TBH it's a bit sad that they turned on the JIT in the current state to begin with; it clearly wasn't ready, and perhaps needed a couple more rounds with the design.
Out of curiosity, are there any copy-and-patch JITs that are clear-cut successes? (Python's JIT is the most high-profile case, and it's definitely not one.)
A huge thank you to all contributors for this gift
I always wondered why sequence numbers weren't replicated, it added another step to the stress of upgrading via pg_backup but thanks for adding it to PG19!
This is the most bug-free .0 release of Postgres. I am always waiting for at least .1 or .2 before upgrading. But should I wait this time?
Personally I would say, for critical production systems, its still good to wait for the .1 release.
Part of why delaying is helpful is that more people will actually install the release than they do during the beta/RC cycle, and (in my read) most of the delay of the release was not necessarily because of significant bugfixing of features that remained in 19 (though e.g. REPACK certainly had its fair share of fixes), but rather the Postgres committers being overly busy with some of the security fixes that just went into 18.7 and the other minors, combined with some late removals of features that warranted an extra beta and RC release.
> Part of why delaying is helpful is that more people will actually install the release than they do during the beta/RC cycle
Unless everybody starts waiting for .1 :)
> was not necessarily because of significant bugfixing in 19
They discovered some serious bugs in new features which weren't really solvable in a way the devs were comfortable with (with regards to long-term maintainability and stability). So some of the new features were rolled back and that process also took some time.
Yep, agreed its bad if everyone does it - but e.g. you could upgrade pre-prod / staging and only do prod once the 19.1 release is out.
To clarify what I meant with the second part: If you look at e.g. SQL/PGQ it was reverted pretty late (beta4), but that revert doesn't mean that other features don't have bugs that are yet to be ironed out. e.g. just this morning a bugfix went in that can crash EXPLAIN (BUFFERS) (without ANALYZE) when you have auto_explain turned on [0]. Edge case, but could happen, and the fix will only be in 19.1 in February 2027.
[0]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...
It really depends on your use-case. Personal use database and you have regular backups, can tolerate some bumps - probably fine to test drive it, but keep an eye open. Serious production system - let it "soak", as they say these days. My personal rule of thumb is 6 months for major versions, it has proven itself many times over many different technologies.
You probably should install it in a test environment. Waiting won't do you any good, if there are load-specific bugs.
Congrats to everyone who worked on this release!
Earlier: https://news.ycombinator.com/item?id=50560357
Found Previous Leon!