Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e67GquW70882 for ; Fri, 7 Jul 2000 12:52:57 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id MAA10715; Fri, 7 Jul 2000 12:52:30 -0400 (EDT) To: Bruce Momjian cc: Peter Eisentraut , Jan Wieck , PostgreSQL HACKERS Subject: Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios... In-reply-to: <200007071602.MAA26710@candle.pha.pa.us> References: <200007071602.MAA26710@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Fri, 07 Jul 2000 12:02:30 -0400" Date: Fri, 07 Jul 2000 12:52:29 -0400 Message-ID: <10712.962988749@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/435 Bruce Momjian 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