Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios.... - Mailing list pgsql-hackers

From JanWieck@t-online.de (Jan Wieck)
Subject Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios....
Date
Msg-id 200007081129.NAA30899@hot.jw.home
Whole thread Raw
In response to Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner wrote:
> At 21:49 7/07/00 -0400, Tom Lane wrote:
> >
> >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.
>
>
> >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?
   It can't. My code is designed for in-memory attribute values.   It doesn't support streaming - which I assume is
requiredfor   pg_dump.
 


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #




pgsql-hackers by date:

Previous
From: "Peter Mount"
Date:
Subject: Re: Contacting me
Next
From: JanWieck@t-online.de (Jan Wieck)
Date:
Subject: Re: fcntl(SETLK) [was Re: 2nd update on TOAST]