From: Philip Warner <pjw@rhyme.com.au>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: PostgreSQL HACKERS <pgsql-hackers@postgresql.org>
Subject: Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
Date: Sat, 08 Jul 2000 12:56:46 +1000
Message-ID: <3.0.5.32.20000708125646.02bf9aa0@mail.rhyme.com.au> (raw)
In-Reply-To: <22942.963023281@sss.pgh.pa.us>
References: <3.0.5.32.20000708120031.00ce8100@mail.rhyme.com.au>
<200007080119.VAA14375@candle.pha.pa.us>
<200007080119.VAA14375@candle.pha.pa.us>
<3.0.5.32.20000708120031.00ce8100@mail.rhyme.com.au>
At 22:28 7/07/00 -0400, Tom Lane wrote:
>
>pg_dump is rather a different case. I would want to see a runtime
>option *not* to use compression
That's there already; using -Z0 produces the same output as a mchine
without zlib.
>But making an uncompressed dump today doesn't invalidate
>the compressed dump you made yesterday, nor vice versa.
Not sure what you mean here.
>Good point. If we include zlib in the distribution it would be pretty
>silly for pg_dump not to use it. If we don't, then Peter's remarks
>about not liking an environment-determined feature set are relevant.
zlib seems to have been ported to zillions of architectures (must be a good
design ;-}), so it's probably pretty safe to put in the source tree, and
I'm sure any porting problems we encounter would be useful to the zlib
maintainers.
If we don't want to use zlib, then fefore using Jan's compression code in
pg_dump, I suppose I'd need to know that the output is compatible across
32/64 bit architectures and is not sensitive to other issues like endian-ness.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: pjw@rhyme.com.au, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us, JanWieck@Yahoo.com, peter_e@gmx.net, pgsql-hackers@postgresql.org
Subject: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
In-Reply-To: <3.0.5.32.20000708125646.02bf9aa0@mail.rhyme.com.au>
References: <3.0.5.32.20000708120031.00ce8100@mail.rhyme.com.au> <200007080119.VAA14375@candle.pha.pa.us> <3.0.5.32.20000708125646.02bf9aa0@mail.rhyme.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox