pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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 17:56:12 -0400
Message-ID: <13864.963006972@sss.pgh.pa.us> (raw)
In-Reply-To: <200007071947.VAA26359@hot.jw.home>
References: <200007071947.VAA26359@hot.jw.home>

JanWieck@t-online.de (Jan Wieck) writes:
> eisentrp@csis.gvsu.edu wrote:
>> Maybe you just want to use zlib. Let other guys hammer out the details.

>     We  cannot  assume that zlib is available everywhere.

We can if we include it in our distribution --- which we could; it's
pretty small and uses a BSD-style license.  I can assure you the zlib
guys would be happy with that.  And it's certainly as portable as our
own code.  The real question is, is a custom compressor enough better
than zlib for our purposes to make it worth taking any patent risks?

We could run zlib at a low compression setting (-z1 to -z3 maybe)
to make compression relatively fast, and since that also doesn't
generate a custom Huffman tree, the overhead in the compressed data
is minor even for short strings.  And its memory footprint is
certainly no worse than Jan's method...

The real question is whether zlib decompression is markedly slower
than Jan's code.  Certainly Jan's method is a lot simpler and *should*
be faster --- but on the other hand, zlib has had a heck of a lot
of careful performance tuning put into it over the years.  The speed
difference might not be as bad as all that.

I think it's worth taking a look at the option.

			regards, tom lane



view thread (29+ messages)  latest in thread

Message-ID: <13864.963006972@sss.pgh.pa.us>
Permalink:  ../13864.963006972@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/13864.963006972@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, JanWieck@Yahoo.com, peter_e@gmx.net, pgsql-hackers@postgresql.org
  Subject: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
  In-Reply-To: <13864.963006972@sss.pgh.pa.us>
  References: <200007071947.VAA26359@hot.jw.home> <13864.963006972@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