Sep 27, 2026 · 12 min · 10 segments
In this episode of Scaling Postgres, we discuss PG19 Beta 4, pgBouncer CVEs, managed provider security and transferring data to Clickhouse using physical replication. To get the show notes as well as…
Creston JamisonHost
The next planned release is the release candidate, which should occur in early October, according to this.

And then hopefully a couple of weeks later, PostgreSQL 19 will be generally available where they say, quote, PostgreSQL 19 GA may also occur in October.

And again, what makes this delay different this year is probably the use of AI and having it find all sorts of edge cases that should be resolved before releasing the product.

Now this is very much true here, quote, the PostgreSQL community strongly believes that first and foremost, PostgreSQL must be reliable, but that also needs to be measured against, quote, striving for a predictable release schedule.

So with those two guidelines, we tend to get things cut to be able to make release dates if they can do it.

And in the changes since beta 3, there aren't as many reverts as was mentioned previously.

We also heard about the online disabling of checksums and temporal updates and deletes provided by 4portionof.

They also removed some pgget functions as well as a change that forced lccollate to C in the postmaster process.

i didn't see that mentioned as well so maybe some of these will still get in don't know we'll have to see but if you want to learn more definitely check out this blog post next piece of content pg bouncer 1.26 is released which fixes three cves and two of these can be caused by unauthenticated clients so definitely important to upgrade this if your pg bouncer is open to the internet which you probably shouldn't do anyway But one of these is caused by a scram client final message without a nuance.

And then the third one, not triggerable by unauthentic clients, is actually when you have a malicious Postgres server.

The next planned release is the release candidate, which should occur in early October, according to this.

And then hopefully a couple of weeks later, PostgreSQL 19 will be generally available where they say, quote, PostgreSQL 19 GA may also occur in October.

And again, what makes this delay different this year is probably the use of AI and having it find all sorts of edge cases that should be resolved before releasing the product.

Now this is very much true here, quote, the PostgreSQL community strongly believes that first and foremost, PostgreSQL must be reliable, but that also needs to be measured against, quote, striving for a predictable release schedule.

So with those two guidelines, we tend to get things cut to be able to make release dates if they can do it.

And in the changes since beta 3, there aren't as many reverts as was mentioned previously.

We also heard about the online disabling of checksums and temporal updates and deletes provided by 4portionof.

They also removed some pgget functions as well as a change that forced lccollate to C in the postmaster process.

i didn't see that mentioned as well so maybe some of these will still get in don't know we'll have to see but if you want to learn more definitely check out this blog post next piece of content pg bouncer 1.26 is released which fixes three cves and two of these can be caused by unauthenticated clients so definitely important to upgrade this if your pg bouncer is open to the internet which you probably shouldn't do anyway But one of these is caused by a scram client final message without a nuance.

And then the third one, not triggerable by unauthentic clients, is actually when you have a malicious Postgres server.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.