pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Philip Warner <pjw@rhyme.com.au>
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: Fri, 07 Jul 2000 22:28:01 -0400
Message-ID: <22942.963023281@sss.pgh.pa.us> (raw)
In-Reply-To: <3.0.5.32.20000708120031.00ce8100@mail.rhyme.com.au>
References: <200007080119.VAA14375@candle.pha.pa.us>
	<200007080119.VAA14375@candle.pha.pa.us>
	<3.0.5.32.20000708120031.00ce8100@mail.rhyme.com.au>

Philip Warner <pjw@rhyme.com.au> writes:
>> Not bloody likely!  Do you want to be in a position where you restart
>> your postmaster and suddenly chunks of your database are inaccessible?
>> That's what could happen to you if someone moves or deletes libz.so.

> My question was limited to it's use in pg_dump; rather than basing
> pg_dump's compression bahaviour on configure, base it on it's runtime
> environment. But my guess is you still would be inclined, rather strongly,
> against it.

pg_dump is rather a different case.  I would want to see a runtime
option *not* to use compression, in case you know you are going to
need to restore on another system where zlib (or whatever) isn't
available.  But making an uncompressed dump today doesn't invalidate
the compressed dump you made yesterday, nor vice versa.

>> If we do go with using zlib instead of homegrown code

> This begs the obvious question: should pg_dump be using Jan's compression
> code? In all cases/when zlib is not available?

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.

			regards, tom lane



view thread (29+ messages)  latest in thread

Message-ID: <22942.963023281@sss.pgh.pa.us>
Permalink:  ../22942.963023281@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22942.963023281@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, pjw@rhyme.com.au, 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: <22942.963023281@sss.pgh.pa.us>
  References: <200007080119.VAA14375@candle.pha.pa.us> <3.0.5.32.20000708120031.00ce8100@mail.rhyme.com.au> <22942.963023281@sss.pgh.pa.us>

* 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