Aug 16, 2026 · 10 min · 10 segments
In this episode of Scaling Postgres, we discuss new releases fixing 28 security vulnerabilities, more MVCC, BYOK encryption and should Postgres include pgbouncer. To get the show notes as well as get…
Creston JamisonHost
Our first piece of content is PostgreSQL 18.6, 17.11, 16.15, 15.19, 14.24, and 19.3 are released.

This is from postgreSQL.org, and these releases fix 28 security vulnerabilities and over 110 bugs over the past several months.

And you'll notice for version 18, there was a gap because 18.5 was not shipped due to a regression.

So basically, we went from 18.4 to 18.6. Now, with this update, you will have to address some index issues.

So there's some additional steps you need to take if you have done parallel gen index builds, if you use btree-gist extension or ltree.

But the full guidance on what you should do is at the bottom here under the updating section.

And a reminder, Postgres 14 End of Life is coming up November 12th, and here are the 28 security issues, which is more than double the last quarter, I think, if I'm remembering correct.

So at this point, if you are leaving your database out and accessible to the internet, I would do what you can to reverse that practice as soon as you can.

Now, there might not be any of these that are remote code execution, but still to my mind it's just got to be a matter of time.

But irrespective, you should probably update your database as soon as you can, and then of course they list the different bugs that were addressed as well if you want to check that out.

Our first piece of content is PostgreSQL 18.6, 17.11, 16.15, 15.19, 14.24, and 19.3 are released.

This is from postgreSQL.org, and these releases fix 28 security vulnerabilities and over 110 bugs over the past several months.

And you'll notice for version 18, there was a gap because 18.5 was not shipped due to a regression.

So basically, we went from 18.4 to 18.6. Now, with this update, you will have to address some index issues.

So there's some additional steps you need to take if you have done parallel gen index builds, if you use btree-gist extension or ltree.

But the full guidance on what you should do is at the bottom here under the updating section.

And a reminder, Postgres 14 End of Life is coming up November 12th, and here are the 28 security issues, which is more than double the last quarter, I think, if I'm remembering correct.

So at this point, if you are leaving your database out and accessible to the internet, I would do what you can to reverse that practice as soon as you can.

Now, there might not be any of these that are remote code execution, but still to my mind it's just got to be a matter of time.

But irrespective, you should probably update your database as soon as you can, and then of course they list the different bugs that were addressed as well if you want to check that out.
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.