Re: WAL compression setting after PostgreSQL LZ4 default change - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: WAL compression setting after PostgreSQL LZ4 default change
Date
Msg-id ak2Es90xR35P2jPB@msg.df7cb.de
Whole thread
In response to Re: WAL compression setting after PostgreSQL LZ4 default change  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: WAL compression setting after PostgreSQL LZ4 default change
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add malloc attribute to memory allocation functions
Next
From: Peter Geoghegan
Date:
Subject: Re: index prefetching