PG 19 status blog report

Started by Bruce Momjian2 days ago5 messageshackers
Jump to latest
#1Bruce Momjian
bruce@momjian.us

I found this blog post about the unusual status of Postgres 19 helpful:

https://www.snowflake.com/en/blog/engineering/postgresql-19-release-delay-feature-reverts/

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

#2Michael Paquier
michael@paquier.xyz
In reply to: Bruce Momjian (#1)
Re: PG 19 status blog report

On Fri, Sep 18, 2026 at 12:27:00PM -0400, Bruce Momjian wrote:

I found this blog post about the unusual status of Postgres 19 helpful:

https://www.snowflake.com/en/blog/engineering/postgresql-19-release-delay-feature-reverts/

The "Default TOAST compression change to lz4" part is incorrect.
34dfca293432 has switched default_toast_compression to lz4 by default
if we compile by lz4. What has been reverted is 4f0b3afab4da, which
forced --with-lz4 across the buildfarm. So we still have a softer
patch in, and using --with-lz4 will enforce a new default.
--
Michael

#3Bruce Momjian
bruce@momjian.us
In reply to: Michael Paquier (#2)
Re: PG 19 status blog report

On Sat, Sep 19, 2026 at 08:56:44AM +0900, Michael Paquier wrote:

On Fri, Sep 18, 2026 at 12:27:00PM -0400, Bruce Momjian wrote:

I found this blog post about the unusual status of Postgres 19 helpful:

https://www.snowflake.com/en/blog/engineering/postgresql-19-release-delay-feature-reverts/

The "Default TOAST compression change to lz4" part is incorrect.
34dfca293432 has switched default_toast_compression to lz4 by default
if we compile by lz4. What has been reverted is 4f0b3afab4da, which
forced --with-lz4 across the buildfarm. So we still have a softer
patch in, and using --with-lz4 will enforce a new default.

Yes, I was surprised about that one too. Glad she was wrong.

--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

#4wenhui qiu
qiuwenhuifx@gmail.com
In reply to: Michael Paquier (#2)
Re: PG 19 status blog report

HI Michael

The "Default TOAST compression change to lz4" part is incorrect.

34dfca293432 has switched default_toast_compression to lz4 by default
if we compile by lz4. What has been reverted is 4f0b3afab4da, which
forced --with-lz4 across the buildfarm. So we still have a softer
patch in, and using --with-lz4 will enforce a new default.

Could we enable --with-lz4 by default, just like --with-readline, instead
of having to specify it explicitly?

Thanks

#5Michael Paquier
michael@paquier.xyz
In reply to: wenhui qiu (#4)
Re: PG 19 status blog report

On Sat, Sep 19, 2026 at 08:50:05PM +0800, wenhui qiu wrote:

The "Default TOAST compression change to lz4" part is incorrect.
34dfca293432 has switched default_toast_compression to lz4 by default
if we compile by lz4. What has been reverted is 4f0b3afab4da, which
forced --with-lz4 across the buildfarm. So we still have a softer
patch in, and using --with-lz4 will enforce a new default.

(The quoting of your previous message was formatted in a weird way,
perhaps you should fix that..)

Could we enable --with-lz4 by default, just like --with-readline, instead
of having to specify it explicitly?

I have heavily broken the buildfarm once when attempting that, and
have no plans to attempt the same thing a second time in the
short-term or even middle-term.
--
Michael