public inbox for [email protected]help / color / mirror / Atom feed
WAL compression setting after PostgreSQL LZ4 default change 12+ messages / 6 participants [nested] [flat]
* WAL compression setting after PostgreSQL LZ4 default change @ 2026-06-30 10:25 wenhui qiu <[email protected]> 0 siblings, 2 replies; 12+ messages in thread From: wenhui qiu @ 2026-06-30 10:25 UTC (permalink / raw) To: pgsql-hackers; +Cc: Japin Li <[email protected]>; John Naylor <[email protected]>; Christoph Berg <[email protected]>; Michael Paquier <[email protected]> HI The recent PostgreSQL commit changes the default TOAST compression to lz4 when LZ4 support is available, based on the rationale that LZ4 is generally more efficient than pglz in terms of CPU usage and compression ratio.Given that, should we also consider changing the default compression method used by wal_compression = on from pglz to lz4? Currently, wal_compression = on still maps to pglz, while lz4 has to be selected explicitly with: wal_compression = lz4 If LZ4 is now considered stable and preferable enough to become the default for TOAST compression, it may be worth aligning WAL compression behavior as well, or at least discussing whether on should continue to imply pglz. Thanks Attachments: [application/octet-stream] v001-wal-compression-on-lz4.patch (2.9K, ../../CAGjGUAL1b=Mwd1SCvLbo+fivEr9KDpFcu4jmqKCZXwT=6CiiGQ@mail.gmail.com/3-v001-wal-compression-on-lz4.patch) download | inline diff: diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 009295f20e9..c7107dec232 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3634,6 +3634,8 @@ include_dir 'conf.d' was compiled with <option>--with-lz4</option>) and <literal>zstd</literal> (if <productname>PostgreSQL</productname> was compiled with <option>--with-zstd</option>). + The value <literal>on</literal> selects <literal>lz4</literal>, if + available; otherwise, it selects <literal>pglz</literal>. The default value is <literal>off</literal>. Only superusers and users with the appropriate <literal>SET</literal> privilege can change this setting. diff --git a/src/backend/utils/misc/guc_tables.c b/src/backend/utils/misc/guc_tables.c index 290ccbc543e..9efd34aafea 100644 --- a/src/backend/utils/misc/guc_tables.c +++ b/src/backend/utils/misc/guc_tables.c @@ -484,13 +484,13 @@ static const struct config_enum_entry wal_compression_options[] = { #ifdef USE_ZSTD {"zstd", WAL_COMPRESSION_ZSTD, false}, #endif - {"on", WAL_COMPRESSION_PGLZ, false}, + {"on", DEFAULT_WAL_COMPRESSION, false}, {"off", WAL_COMPRESSION_NONE, false}, - {"true", WAL_COMPRESSION_PGLZ, true}, + {"true", DEFAULT_WAL_COMPRESSION, true}, {"false", WAL_COMPRESSION_NONE, true}, - {"yes", WAL_COMPRESSION_PGLZ, true}, + {"yes", DEFAULT_WAL_COMPRESSION, true}, {"no", WAL_COMPRESSION_NONE, true}, - {"1", WAL_COMPRESSION_PGLZ, true}, + {"1", DEFAULT_WAL_COMPRESSION, true}, {"0", WAL_COMPRESSION_NONE, true}, {NULL, 0, false} }; diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample index ac38cddaaf9..d3e060b2111 100644 --- a/src/backend/utils/misc/postgresql.conf.sample +++ b/src/backend/utils/misc/postgresql.conf.sample @@ -263,6 +263,7 @@ # (change requires restart) #wal_compression = off # enables compression of full-page writes; # off, pglz, lz4, zstd, or on + # (on = lz4 if available, else pglz) #wal_init_zero = on # zero-fill new WAL files #wal_recycle = on # recycle WAL files #wal_buffers = -1 # min 32kB, -1 sets based on shared_buffers diff --git a/src/include/access/xlog.h b/src/include/access/xlog.h index 437b4f32349..4dad4e47cbf 100644 --- a/src/include/access/xlog.h +++ b/src/include/access/xlog.h @@ -87,6 +87,16 @@ typedef enum WalCompression WAL_COMPRESSION_ZSTD, } WalCompression; +/* + * Choose an appropriate default WAL compression method for wal_compression=on. + * If LZ4 is compiled in, use it; otherwise, use pglz. + */ +#ifdef USE_LZ4 +#define DEFAULT_WAL_COMPRESSION WAL_COMPRESSION_LZ4 +#else +#define DEFAULT_WAL_COMPRESSION WAL_COMPRESSION_PGLZ +#endif + /* Recovery states */ typedef enum RecoveryState { ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-06-30 10:51 Christoph Berg <[email protected]> parent: wenhui qiu <[email protected]> 1 sibling, 1 reply; 12+ messages in thread From: Christoph Berg @ 2026-06-30 10:51 UTC (permalink / raw) To: wenhui qiu <[email protected]>; +Cc: pgsql-hackers; Japin Li <[email protected]>; John Naylor <[email protected]>; Michael Paquier <[email protected]> Re: wenhui qiu > The recent PostgreSQL commit changes the default TOAST compression to lz4 > when LZ4 support is available, based on the rationale that LZ4 is generally > more efficient than pglz in terms of CPU usage and compression ratio.Given > that, should we also consider changing the default compression method used > by wal_compression = on from pglz to lz4? +1 from me. I would prefer this patch over the doc-only one that I sent in the other thread. This should go into PG19 so we don't have two different versions that flip the default from pglz to lz4. Christoph ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-06-30 13:48 Japin Li <[email protected]> parent: Christoph Berg <[email protected]> 0 siblings, 0 replies; 12+ messages in thread From: Japin Li @ 2026-06-30 13:48 UTC (permalink / raw) To: Christoph Berg <[email protected]>; +Cc: wenhui qiu <[email protected]>; pgsql-hackers; John Naylor <[email protected]>; Michael Paquier <[email protected]> On Tue, 30 Jun 2026 at 12:51, Christoph Berg <[email protected]> wrote: > Re: wenhui qiu >> The recent PostgreSQL commit changes the default TOAST compression to lz4 >> when LZ4 support is available, based on the rationale that LZ4 is generally >> more efficient than pglz in terms of CPU usage and compression ratio.Given >> that, should we also consider changing the default compression method used >> by wal_compression = on from pglz to lz4? > > +1 from me. I would prefer this patch over the doc-only one that I > sent in the other thread. > > This should go into PG19 so we don't have two different versions that > flip the default from pglz to lz4. > +1. LGTM. > Christoph -- Regards, Japin Li ChengDu WenWu Information Technology Co., Ltd. ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-06-30 23:45 Michael Paquier <[email protected]> parent: wenhui qiu <[email protected]> 1 sibling, 2 replies; 12+ messages in thread From: Michael Paquier @ 2026-06-30 23:45 UTC (permalink / raw) To: wenhui qiu <[email protected]>; +Cc: pgsql-hackers; Japin Li <[email protected]>; John Naylor <[email protected]>; Christoph Berg <[email protected]> On Tue, Jun 30, 2026 at 06:25:09PM +0800, wenhui qiu wrote: > The recent PostgreSQL commit changes the default TOAST compression to lz4 > when LZ4 support is available, based on the rationale that LZ4 is generally > more efficient than pglz in terms of CPU usage and compression > ratio. Given that, should we also consider changing the default > compression method used by wal_compression = on from pglz to lz4? "on" is just a backward-compatible value, so we could let it as-is. > Currently, wal_compression = on still maps to pglz, while lz4 has to be > selected explicitly with: > > wal_compression = lz4 > If LZ4 is now considered stable and preferable enough to become the default > for TOAST compression, it may be worth aligning WAL compression behavior as > well, or at least discussing whether on should continue to imply pglz. If I were switch the default, for me zstd goes first, lz4 is a close second, and pglz is the last of its class. The only reason why we have not chosen zstd for TOAST is the fact that we don't support it (trickier to add support for it as we have to preserve on-disk compatibility for inline compressed TOAST entries). In short, lz4 is available in many environments, but I'm also ready to bet that zstd is equally available in these environments. -- Michael Attachments: [application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc) download ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-01 01:53 wenhui qiu <[email protected]> parent: Michael Paquier <[email protected]> 1 sibling, 1 reply; 12+ messages in thread From: wenhui qiu @ 2026-07-01 01:53 UTC (permalink / raw) To: Michael Paquier <[email protected]>; +Cc: pgsql-hackers; Japin Li <[email protected]>; John Naylor <[email protected]>; Christoph Berg <[email protected]> Hi Michael > > > If I were switch the default, for me zstd goes first, lz4 is a close > > second, and pglz is the last of its class. The only reason why we > > have not chosen zstd for TOAST is the fact that we don't support it > > (trickier to add support for it as we have to preserve on-disk > > compatibility for inline compressed TOAST entries). > > > In short, lz4 is available in many environments, but I'm also ready to > > bet that zstd is equally available in these environments. > Thanks for the feedback. > > Yes, I did consider zstd as well. I agree that zstd can provide a better > compression ratio than lz4, and if we only look at compression ratio, zstd > is > a very attractive choice. > > The reason I started with lz4 was mainly to keep this change aligned with > the > recent TOAST compression change. Since lz4 has already been accepted there > as > the preferred default when available, I thought using the same choice for > wal_compression=on would make the proposal smaller, more consistent, and > easier > to evaluate. so > > Second, WAL compression happens on the WAL insertion path for full-page > images, > so compression speed and CPU overhead matter a lot. lz4 is generally a > good fit > for that trade-off: it still reduces WAL volume, while keeping compression > latency and CPU cost lower than zstd in many workloads. > > That said, I understand the argument for preferring zstd when it is > available. > I have prepared an alternative version where wal_compression=on selects > zstd > first, then lz4 if zstd is not available, and finally pglz as the fallback > Thanks Attachments: [application/octet-stream] v002-wal-compression-on-zstd-lz4.patch (3.1K, ../../CAGjGUAJaGmTwSSiF2so69Pjmjo4zwhsA+dmcUGRmqM856K9pBA@mail.gmail.com/3-v002-wal-compression-on-zstd-lz4.patch) download | inline diff: diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index 009295f20e9..2282c9e99b8 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -3634,6 +3634,9 @@ include_dir 'conf.d' was compiled with <option>--with-lz4</option>) and <literal>zstd</literal> (if <productname>PostgreSQL</productname> was compiled with <option>--with-zstd</option>). + The value <literal>on</literal> selects <literal>zstd</literal>, if + available; otherwise, it selects <literal>lz4</literal>, if available; + otherwise, it selects <literal>pglz</literal>. The default value is <literal>off</literal>. Only superusers and users with the appropriate <literal>SET</literal> privilege can change this setting. diff --git a/src/backend/utils/misc/guc_tables.c b/src/backend/utils/misc/guc_tables.c index 290ccbc543e..9efd34aafea 100644 --- a/src/backend/utils/misc/guc_tables.c +++ b/src/backend/utils/misc/guc_tables.c @@ -484,13 +484,13 @@ static const struct config_enum_entry wal_compression_options[] = { #ifdef USE_ZSTD {"zstd", WAL_COMPRESSION_ZSTD, false}, #endif - {"on", WAL_COMPRESSION_PGLZ, false}, + {"on", DEFAULT_WAL_COMPRESSION, false}, {"off", WAL_COMPRESSION_NONE, false}, - {"true", WAL_COMPRESSION_PGLZ, true}, + {"true", DEFAULT_WAL_COMPRESSION, true}, {"false", WAL_COMPRESSION_NONE, true}, - {"yes", WAL_COMPRESSION_PGLZ, true}, + {"yes", DEFAULT_WAL_COMPRESSION, true}, {"no", WAL_COMPRESSION_NONE, true}, - {"1", WAL_COMPRESSION_PGLZ, true}, + {"1", DEFAULT_WAL_COMPRESSION, true}, {"0", WAL_COMPRESSION_NONE, true}, {NULL, 0, false} }; diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample index ac38cddaaf9..43cb28fce48 100644 --- a/src/backend/utils/misc/postgresql.conf.sample +++ b/src/backend/utils/misc/postgresql.conf.sample @@ -263,6 +263,8 @@ # (change requires restart) #wal_compression = off # enables compression of full-page writes; # off, pglz, lz4, zstd, or on + # (on = zstd if available, else lz4 if + # available, else pglz) #wal_init_zero = on # zero-fill new WAL files #wal_recycle = on # recycle WAL files #wal_buffers = -1 # min 32kB, -1 sets based on shared_buffers diff --git a/src/include/access/xlog.h b/src/include/access/xlog.h index 437b4f32349..a7c46352b30 100644 --- a/src/include/access/xlog.h +++ b/src/include/access/xlog.h @@ -87,6 +87,19 @@ typedef enum WalCompression WAL_COMPRESSION_ZSTD, } WalCompression; +/* + * Choose an appropriate default WAL compression method for wal_compression=on. + * Prefer zstd when compiled in; otherwise use lz4 if available, falling back + * to pglz. + */ +#ifdef USE_ZSTD +#define DEFAULT_WAL_COMPRESSION WAL_COMPRESSION_ZSTD +#elif defined(USE_LZ4) +#define DEFAULT_WAL_COMPRESSION WAL_COMPRESSION_LZ4 +#else +#define DEFAULT_WAL_COMPRESSION WAL_COMPRESSION_PGLZ +#endif + /* Recovery states */ typedef enum RecoveryState { ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-03 02:18 Japin Li <[email protected]> parent: wenhui qiu <[email protected]> 0 siblings, 0 replies; 12+ messages in thread From: Japin Li @ 2026-07-03 02:18 UTC (permalink / raw) To: wenhui qiu <[email protected]>; +Cc: Michael Paquier <[email protected]>; pgsql-hackers; John Naylor <[email protected]>; Christoph Berg <[email protected]> On Wed, 01 Jul 2026 at 09:53, wenhui qiu <[email protected]> wrote: > Hi Michael > > > If I were switch the default, for me zstd goes first, lz4 is a close > > second, and pglz is the last of its class. The only reason why we > > have not chosen zstd for TOAST is the fact that we don't support it > > (trickier to add support for it as we have to preserve on-disk > > compatibility for inline compressed TOAST entries). > > > In short, lz4 is available in many environments, but I'm also ready to > > bet that zstd is equally available in these environments. > Thanks for the feedback. > > Yes, I did consider zstd as well. I agree that zstd can provide a better > compression ratio than lz4, and if we only look at compression ratio, zstd is > a very attractive choice. > > The reason I started with lz4 was mainly to keep this change aligned with the > recent TOAST compression change. Since lz4 has already been accepted there as > the preferred default when available, I thought using the same choice for > wal_compression=on would make the proposal smaller, more consistent, and easier > to evaluate. so > > Second, WAL compression happens on the WAL insertion path for full-page images, > so compression speed and CPU overhead matter a lot. lz4 is generally a good fit > for that trade-off: it still reduces WAL volume, while keeping compression > latency and CPU cost lower than zstd in many workloads. > > That said, I understand the argument for preferring zstd when it is available. > I have prepared an alternative version where wal_compression=on selects zstd > first, then lz4 if zstd is not available, and finally pglz as the fallback > > Thanks Thanks for updating the patch. I've registered it in the CommitFest [1]. [1] https://commitfest.postgresql.org/patch/6979/ -- Regards, Japin Li ChengDu WenWu Information Technology Co., Ltd. ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-03 02:58 Fujii Masao <[email protected]> parent: Michael Paquier <[email protected]> 1 sibling, 1 reply; 12+ messages in thread From: Fujii Masao @ 2026-07-03 02:58 UTC (permalink / raw) To: Michael Paquier <[email protected]>; +Cc: wenhui qiu <[email protected]>; pgsql-hackers; Japin Li <[email protected]>; John Naylor <[email protected]>; Christoph Berg <[email protected]> On Wed, Jul 1, 2026 at 8:45 AM Michael Paquier <[email protected]> wrote: > > On Tue, Jun 30, 2026 at 06:25:09PM +0800, wenhui qiu wrote: > > The recent PostgreSQL commit changes the default TOAST compression to lz4 > > when LZ4 support is available, based on the rationale that LZ4 is generally > > more efficient than pglz in terms of CPU usage and compression > > ratio. Given that, should we also consider changing the default > > compression method used by wal_compression = on from pglz to lz4? > > "on" is just a backward-compatible value, so we could let it as-is. Yes, so +1 to leaving "on" as it is. Making its meaning depend on the build options seems very confusing. Users who want lz4 or zstd can simply specify those methods explicitly instead of using "on". Regards, -- Fujii Masao ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-03 08:38 Japin Li <[email protected]> parent: Fujii Masao <[email protected]> 0 siblings, 1 reply; 12+ messages in thread From: Japin Li @ 2026-07-03 08:38 UTC (permalink / raw) To: Fujii Masao <[email protected]>; +Cc: Michael Paquier <[email protected]>; wenhui qiu <[email protected]>; pgsql-hackers; John Naylor <[email protected]>; Christoph Berg <[email protected]> On Fri, 03 Jul 2026 at 11:58, Fujii Masao <[email protected]> wrote: > On Wed, Jul 1, 2026 at 8:45 AM Michael Paquier <[email protected]> wrote: >> >> On Tue, Jun 30, 2026 at 06:25:09PM +0800, wenhui qiu wrote: >> > The recent PostgreSQL commit changes the default TOAST compression to lz4 >> > when LZ4 support is available, based on the rationale that LZ4 is generally >> > more efficient than pglz in terms of CPU usage and compression >> > ratio. Given that, should we also consider changing the default >> > compression method used by wal_compression = on from pglz to lz4? >> >> "on" is just a backward-compatible value, so we could let it as-is. > > Yes, so +1 to leaving "on" as it is. Making its meaning depend on > the build options seems very confusing. Users who want lz4 or zstd > can simply specify those methods explicitly instead of using "on". > Understood. I'll withdraw this from the CommitFest. > Regards, > > -- > Fujii Masao -- Regards, Japin Li ChengDu WenWu Information Technology Co., Ltd. ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-07 22:26 Michael Paquier <[email protected]> parent: Japin Li <[email protected]> 0 siblings, 1 reply; 12+ messages in thread From: Michael Paquier @ 2026-07-07 22:26 UTC (permalink / raw) To: Japin Li <[email protected]>; +Cc: Fujii Masao <[email protected]>; wenhui qiu <[email protected]>; pgsql-hackers; John Naylor <[email protected]>; Christoph Berg <[email protected]> On Fri, Jul 03, 2026 at 04:38:06PM +0800, Japin Li wrote: > On Fri, 03 Jul 2026 at 11:58, Fujii Masao <[email protected]> wrote: >> On Wed, Jul 1, 2026 at 8:45 AM Michael Paquier <[email protected]> wrote: >>> >>> On Tue, Jun 30, 2026 at 06:25:09PM +0800, wenhui qiu wrote: >>> > The recent PostgreSQL commit changes the default TOAST compression to lz4 >>> > when LZ4 support is available, based on the rationale that LZ4 is generally >>> > more efficient than pglz in terms of CPU usage and compression >>> > ratio. Given that, should we also consider changing the default >>> > compression method used by wal_compression = on from pglz to lz4? >>> >>> "on" is just a backward-compatible value, so we could let it as-is. >> >> Yes, so +1 to leaving "on" as it is. Making its meaning depend on >> the build options seems very confusing. Users who want lz4 or zstd >> can simply specify those methods explicitly instead of using "on". > > Understood. I'll withdraw this from the CommitFest. I disagree. The whole argument is that most users don't bother changing the defaults. Here, a change between lz4/zstd and pglz is like day and night; folks are going to see improvements all the time if we switch to a better default when we can, in terms of CPU, memory and IO. -- Michael Attachments: [application/pgp-signature] signature.asc (833B, ../../[email protected]/2-signature.asc) download ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-07 22:46 Jelte Fennema-Nio <[email protected]> parent: Michael Paquier <[email protected]> 0 siblings, 1 reply; 12+ messages in thread From: Jelte Fennema-Nio @ 2026-07-07 22:46 UTC (permalink / raw) To: Michael Paquier <[email protected]>; +Cc: Japin Li <[email protected]>; Fujii Masao <[email protected]>; wenhui qiu <[email protected]>; pgsql-hackers; John Naylor <[email protected]>; Christoph Berg <[email protected]> On Wed, 8 Jul 2026 at 00:26, Michael Paquier <[email protected]> wrote: > I disagree. The whole argument is that most users don't bother > changing the defaults. Here, a change between lz4/zstd and pglz is > like day and night; folks are going to see improvements all the time > if we switch to a better default when we can, in terms of CPU, memory > and IO. A small correction though: "on" isn't the default. The default is "off". So this would only impact users who changed the setting in their cluster to "on" at some point in the past when lz4/zstd support did not exist yet. So we wouldn't be changing the default. We'd be changing the behavior for people who changed their default setting at some point. To be clear, I agree with you that that's a reasonable thing to do; I don't think any of those people actually want to burn CPU for no reason. So they'd all be happy if we stopped doing that. pglz basically has no right to be used anywhere in production systems IMO. ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-07 22:58 Christoph Berg <[email protected]> parent: Jelte Fennema-Nio <[email protected]> 0 siblings, 1 reply; 12+ messages in thread From: Christoph Berg @ 2026-07-07 22:58 UTC (permalink / raw) To: Jelte Fennema-Nio <[email protected]>; +Cc: Michael Paquier <[email protected]>; Japin Li <[email protected]>; Fujii Masao <[email protected]>; wenhui qiu <[email protected]>; pgsql-hackers; John Naylor <[email protected]> Re: Jelte Fennema-Nio > A small correction though: "on" isn't the default. The default is > "off". So this would only impact users who changed the setting in > their cluster to "on" at some point in the past when lz4/zstd support > did not exist yet. So we wouldn't be changing the default. We'd be > changing the behavior for people who changed their default setting at > some point. If someone just wants compression and not bother with the ugly details of compression algorithms, they might be inclined to just say "on". By labelling one of the choices with this "easy" value, we are effectively promoting pglz as a good choice. (I'm definitely one of those people, if you give me too many options, I will look for some hint what to do or walk away. Now 3 isn't "too many" but you get the idea.) I would like to see "on" to be moved to some better value (likely lz4, like toast compression), and if some day, there is yet a better choice, we should move it again. Christoph ^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: WAL compression setting after PostgreSQL LZ4 default change @ 2026-07-08 06:37 wenhui qiu <[email protected]> parent: Christoph Berg <[email protected]> 0 siblings, 0 replies; 12+ messages in thread From: wenhui qiu @ 2026-07-08 06:37 UTC (permalink / raw) To: Christoph Berg <[email protected]>; Jelte Fennema-Nio <[email protected]>; Michael Paquier <[email protected]>; Japin Li <[email protected]>; Fujii Masao <[email protected]>; wenhui qiu <[email protected]>; pgsql-hackers; John Naylor <[email protected]> Hi > I would like to see "on" to be moved to some better value (likely lz4, > > like toast compression), and if some day, there is yet a better > > choice, we should move it again. > Yes, After PostgreSQL 19, lz4 became a required dependency unless you > compile it yourself with --without-lz4. In most environments, lz4 is > already installed, so along this code path the effective choice is > essentially fixed to lz4.At cluster scale, it would make more sense to > expose this parameter in the frontend as a boolean setting, rather than > letting users choose from multiple compression options. Thanks ^ permalink raw reply [nested|flat] 12+ messages in thread
end of thread, other threads:[~2026-07-08 06:37 UTC | newest] Thread overview: 12+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2026-06-30 10:25 WAL compression setting after PostgreSQL LZ4 default change wenhui qiu <[email protected]> 2026-06-30 10:51 ` Christoph Berg <[email protected]> 2026-06-30 13:48 ` Japin Li <[email protected]> 2026-06-30 23:45 ` Michael Paquier <[email protected]> 2026-07-01 01:53 ` wenhui qiu <[email protected]> 2026-07-03 02:18 ` Japin Li <[email protected]> 2026-07-03 02:58 ` Fujii Masao <[email protected]> 2026-07-03 08:38 ` Japin Li <[email protected]> 2026-07-07 22:26 ` Michael Paquier <[email protected]> 2026-07-07 22:46 ` Jelte Fennema-Nio <[email protected]> 2026-07-07 22:58 ` Christoph Berg <[email protected]> 2026-07-08 06:37 ` wenhui qiu <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox