Re: Refactoring of compression options in pg_basebackup
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Magnus Hagander <magnus@hagander.net>
Cc: Robert Haas <robertmhaas@gmail.com>, Georgios Kokolatos <gkokolatos@pm.me>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Jeevan Ladhe <jeevan.ladhe@enterprisedb.com>
Date: 2022-01-17T03:56:06Z
Lists: pgsql-hackers
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. -- Michael
Commits
-
Extend the options of pg_basebackup to control compression
- 5c649fe15336 15.0 landed
-
Add TAP tests for pg_basebackup with compression
- 50e144193c77 15.0 landed
-
Refactor tar method of walmethods.c to rely on the compression method
- 000f3adfdc43 15.0 landed