Re: Refactoring of compression options in pg_basebackup

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Georgios Kokolatos <gkokolatos(at)pm(dot)me>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>
Subject: Re: Refactoring of compression options in pg_basebackup
Date: 2022-01-17 14:29:02
Message-ID: CABUevEx99jnXPJ+Tansf_DcoE=LC5uHR-HrduTTAGe8dfCU9=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jan 17, 2022 at 4:56 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Sat, Jan 15, 2022 at 04:15:26PM +0100, Magnus Hagander wrote:
> > I think having --client-compress and --server-compress separately but
> > having --compression-level *not* being separate would be confusing and
> > I *think* that's what the current patch proposes?
>
> Yep, your understanding is right. The last version of the patch
> posted does exactly that.

Ok. Then that is exactly what I think is confusing, and thus object to :)

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2022-01-17 14:43:30 Blank archive_command
Previous Message Magnus Hagander 2022-01-17 14:27:38 Re: Refactoring of compression options in pg_basebackup