Re: Refactoring of compression options in pg_basebackup - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Refactoring of compression options in pg_basebackup
Date
Msg-id YeeTMHzZILvX6MaI@paquier.xyz
Whole thread Raw
In response to Re: Refactoring of compression options in pg_basebackup  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Refactoring of compression options in pg_basebackup
Re: Refactoring of compression options in pg_basebackup
List pgsql-hackers
On Tue, Jan 18, 2022 at 10:04:56AM -0500, Robert Haas wrote:
> I think it could make sense for you implement
> --compress=METHOD[:LEVEL], keeping -z and -Z N as synonyms for
> --compress=gzip and --compress=gzip:N, and with --compress=N being
> interpreted as --compress=gzip:N. Then I'll generalize that to
> --compress=[{client|server}-]METHOD[:LEVEL] on the other thread. I
> think we should leave it where, if you don't say either client or
> server, you get client, because that's the historical behavior.
>
> If that doesn't work for you, please let me know what you would prefer.

WFM.  Attached is a patch that extends --compress to handle a method
with an optional compression level.  Some extra tests are added to
cover all that.

Thoughts?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Adding CI to our tree
Next
From: Andrey Borodin
Date:
Subject: Re: [PATCH] reduce page overlap of GiST indexes built using sorted method