pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Philip Warner <pjw@rhyme.com.au>
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 21:49:53 -0400
Message-ID: <19527.963020993@sss.pgh.pa.us> (raw)
In-Reply-To: <200007080119.VAA14375@candle.pha.pa.us>
References: <200007080119.VAA14375@candle.pha.pa.us>

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

> We do dynamic loading for functions.  Not sure if we want to load zlib
> dynamically if we can help it.

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.

I don't mind being dynamically linked to standard system shared libs;
if libc.so is busted then whether Postgres launches is the least of
your worries.  But dynamic dependence on an optional package that's
probably living in /usr/local strikes me as exceedingly risky.

If we do go with using zlib instead of homegrown code, I would recommend
building and statically linking to our own copy even if there is a copy
available on the system.  This will prevent cross-version compatibility
problems as well as where'd-my-library-go syndrome.  We cannot afford
those sorts of risks for something that could prevent us from reading
our database.

			regards, tom lane



view thread (29+ messages)  latest in thread

Message-ID: <19527.963020993@sss.pgh.pa.us>
Permalink:  ../19527.963020993@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/19527.963020993@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, pgman@candle.pha.pa.us, pjw@rhyme.com.au, JanWieck@Yahoo.com, peter_e@gmx.net, pgsql-hackers@postgresql.org
  Subject: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
  In-Reply-To: <19527.963020993@sss.pgh.pa.us>
  References: <200007080119.VAA14375@candle.pha.pa.us> <19527.963020993@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