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/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
