>Well, that would mean linking pg_dump with the library providing the compression you want. I suppose, only data is
compressed,not the whole dump, e.g. dumping without compression then compressing is different from dumping with
compression.
Yep,
I have no skill in C programming, but wouldn't it be a good idea to add/integrate the pigz source in pg_dump ? There is
aleast no concern to have about the License.
regards,
Marc
-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tino Schwarze
Sent: Friday, October 23, 2009 4:25 PM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_dump custom format and pigz
Hi Marc,
On Fri, Oct 23, 2009 at 03:52:16PM +0200, Marc Mamin wrote:
> > You might add pigz as a post-processing step and disabling compression in pg_dump.
>
> The problem with this solution is that it make it necessary to
> decompress the dump entirely before using pg_restore (or did I miss a
> point ?) This is an issue as our uncompressed dumps may reach 3-500
> GB...
Right, that would not work.
> A better way would be to have a configuration option to tell which
> compression tool should be used internally by pg_dump.
Well, that would mean linking pg_dump with the library providing the compression you want. I suppose, only data is
compressed,not the whole dump, e.g. dumping without compression then compressing is different from dumping with
compression.
Tino.
--
"What we nourish flourishes." - "Was wir nähren erblüht."
www.lichtkreis-chemnitz.de
www.tisc.de
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
