pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Philip Warner <pjw@rhyme.com.au>
To: Jan Wieck <JanWieck@Yahoo.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL HACKERS <pgsql-hackers@postgresql.org>
Subject: Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
Date: Sat, 08 Jul 2000 11:16:36 +1000
Message-ID: <3.0.5.32.20000708111636.009b5100@mail.rhyme.com.au> (raw)
In-Reply-To: <200007071947.VAA26359@hot.jw.home>
References: <Pine.LNX.4.21.0007070911430.12287-100000@eos05.csis.gvsu.edu>

At 21:47 7/07/00 +0200, Jan Wieck wrote:
>
>    And how should binary distributions like RPM's handle  it?  I
>    assume  that  this  problem is already on it's way because of
>    the integration of zlib into pg_dump. The only way I  see  is
>    having  different  RPM's  for  each  possible  combination of
>    available helper libs.  Or  is  there  another  way  to  work
>    around?

This remoinded me of a question I wanted to ask Unix people: other OSs I
use allow for dynamic linking, at runtime and in code, against shared
libraries, and I know Unix must allow this. The places where zlib is used
are pretty limited, so it might be worth considering doing the 'HAVE_ZLIB'
kinds of checks at runtime. Then one binary fits all...

Is this hard or easy - at least on machines with a libz.so?

Is it worth doing?

I guess the alternative on rpm is to create both: pg_dump.zlib and
pg_dump.nozlib, and install the right one?


----------------------------------------------------------------
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   |/



view thread (29+ messages)  latest in thread

Message-ID: <3.0.5.32.20000708111636.009b5100@mail.rhyme.com.au>
Permalink:  ../3.0.5.32.20000708111636.009b5100@mail.rhyme.com.au/
Also on:    postgresql.org/message-id/3.0.5.32.20000708111636.009b5100@mail.rhyme.com.au

 · 

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: pjw@rhyme.com.au, JanWieck@Yahoo.com, peter_e@gmx.net, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
  In-Reply-To: <3.0.5.32.20000708111636.009b5100@mail.rhyme.com.au>
  References: <Pine.LNX.4.21.0007070911430.12287-100000@eos05.csis.gvsu.edu> <3.0.5.32.20000708111636.009b5100@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