Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
Date: 2000-07-07 16:52:29
Message-ID: 10712.962988749@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-sql

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> Unless the differential is huge we might want to just skip the
>> patent worries.

> If we found later that there was a patent problem, could we just issue a
> new release with a new compression algorithm?

Yeah, we could, and it could presumably even be a fully compatible
dot-release with no change to the on-disk representation. That
representation and consequently the decompression algorithm are safe
enough, it's the details of the compressor's search for matching
patterns that are a patent minefield.

However, changing the code after-the-fact might not be enough to keep us
from being sued :-(. I'd rather use something that's pretty well
established as being in the clear...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Yves Dorfsman 2000-07-07 17:23:26 images
Previous Message Randall Parker 2000-07-07 16:45:09 JDBC: Encrypted connections? SSL?

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert B. Easter 2000-07-07 16:53:27 Re: Re: [HACKERS] Re: [SQL] MAX() of 0 records.
Previous Message Chris Bitmead 2000-07-07 16:50:53 libpq / SQL3

Browse pgsql-sql by date

  From Date Subject
Next Message Robert B. Easter 2000-07-07 16:53:27 Re: Re: [HACKERS] Re: [SQL] MAX() of 0 records.
Previous Message Tom Lane 2000-07-07 16:35:14 Re: Re: [HACKERS] Re: [SQL] MAX() of 0 records.