Re: adding 'zstd' as a compression algorithm - Mailing list pgsql-hackers

From Tom Lane
Subject Re: adding 'zstd' as a compression algorithm
Date
Msg-id 3240825.1644976575@sss.pgh.pa.us
Whole thread Raw
In response to Re: adding 'zstd' as a compression algorithm  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: adding 'zstd' as a compression algorithm  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Feb 15, 2022 at 7:09 PM David Steele <david@pgmasters.net> wrote:
>> This is even more true for zstd since it is not as ubiquitous as lz4. In
>> fact, it is not even included with base RHEL8. You need to install EPEL
>> to get zstd.

> Yeah, I agree. One thing I was thinking about but didn't include in
> the previous email is that if we did choose to make something like LZ4
> the default, it would presumably only be the default on builds that
> include LZ4 support. Other builds would need to use something else,
> unless we just chose to make LZ4 a hard requirement, which would be
> bolder than we usually are. And that has the consequence that you
> mention. It's something we should consider as we think about changing
> defaults.

Yeah.  I'm +1 on adding zstd as an option, but I think we need to
move *very* slowly on changing any defaults for user-accessible
data (like backup files).  Maybe we have a bit more flexibility
for TOAST, not sure.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: adding 'zstd' as a compression algorithm
Next
From: Thomas Munro
Date:
Subject: Re: USE_BARRIER_SMGRRELEASE on Linux?