Re: Teach pg_receivewal to use lz4 compression - Mailing list pgsql-hackers

From gkokolatos@pm.me
Subject Re: Teach pg_receivewal to use lz4 compression
Date
Msg-id 98dDHVqTFjZbSkNWXboFJwkOhbR0l6v72vtj31Zels9d5P9wmLxTKqdaipQjkRFEhafwNU3Ds_V0NC8hrpu_JqEJ3JHVIzTIRKNv_IjmVJ4=@pm.me
Whole thread Raw
In response to Re: Teach pg_receivewal to use lz4 compression  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Teach pg_receivewal to use lz4 compression
List pgsql-hackers

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Wednesday, November 3rd, 2021 at 12:23 AM, Michael Paquier <michael@paquier.xyz> wrote:

> On Tue, Nov 02, 2021 at 12:31:47PM -0400, Robert Haas wrote:
>> On Tue, Nov 2, 2021 at 8:17 AM Magnus Hagander magnus@hagander.net wrote:
>>> I think for the end user, it is strictly better to name it "gzip",
>>> and given that the target of this option is the end user we should
>>> do so. (It'd be different it we were talking about a build-time
>>> parameter to configure).
>>
>> I agree. Also, I think there's actually a file format called "zlib"
>> which is slightly different from the "gzip" format, and you have to be
>> careful not to generate the wrong one.
>
> Okay, fine by me.  It would be better to be also consistent in
> WalCompressionMethods once we switch to this option value, then.

I will revert to gzip for version 9. Should be out shortly.

Cheers,
//Georgios
>
> Michael



pgsql-hackers by date:

Previous
From: Victor Spirin
Date:
Subject: Re: Atomic rename feature for Windows.
Next
From: Andrey Borodin
Date:
Subject: Re: lastOverflowedXid does not handle transaction ID wraparound