Re: Is a plan for lmza commpression in pg_dump

From: Andrew Chernow <ac(at)esilo(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: daveg <daveg(at)sonic(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Dann Corbit <DCorbit(at)connx(dot)com>, Stanislav Lacko <lacko(at)spacesystems(dot)sk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Is a plan for lmza commpression in pg_dump
Date: 2009-02-08 22:37:29
Message-ID: 498F5EA9.5060309@esilo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut wrote:
>
> Notice that the thread originally called for lzma support, which is
> completely at the opposite end of the spectrum of compression algorithms
> in terms of space and time, compared to lzo. So it's not really clear
> what the requirements are in the first place.
>
>

Instead of trying to figure out the needs/wants of a DBA, a general purpose
solution, it might be better to figure out how to make the compression choice
user-driven. Maybe the requirement should be to make this the user's decision;
pipe'n the output to the compression of choice seems to be the simplest approach.

There are cases the highest compression is desired even if it takes forever, and
cases for just the opposite. Not sure why this has to be builtin or why it much
use zlib, other than this is the current method.

--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2009-02-08 23:12:18 Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Previous Message Peter Eisentraut 2009-02-08 22:12:06 Re: Python 3.0 does not work with PL/Python