Received: from clio.trends.ca (root@clio.trends.ca [209.47.148.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e66FfEW51688; Thu, 6 Jul 2000 11:41:14 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by clio.trends.ca (8.9.3+Sun/8.9.3) with ESMTP id KAA19966; Thu, 6 Jul 2000 10:23:02 -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 KAA29097; Thu, 6 Jul 2000 10:22:55 -0400 (EDT) To: Jan Wieck cc: PostgreSQL GENERAL , PostgreSQL HACKERS , PostgreSQL SQL Subject: Re: lztext and compression ratios... In-reply-to: <200007060847.KAA16369@hot.jw.home> References: <200007060847.KAA16369@hot.jw.home> Comments: In-reply-to JanWieck@t-online.de (Jan Wieck) message dated "Thu, 06 Jul 2000 10:47:24 +0200" Date: Thu, 06 Jul 2000 10:22:55 -0400 Message-ID: <29094.962893375@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/243 JanWieck@t-online.de (Jan Wieck) writes: >> As long as you brought it up: how sure are you that the method you've >> used is not subject to any patents? > Now that you ask for it: I'm not sure. Could be. >> If you can show that this method uses no ideas not found in zlib, >> then I'll feel reassured > To do so I don't know enough about the algorithms used in > zlib. Is there someone out here who could verify that if I > detailed enough describe what our compression code does? After a quick look at the code, I don't think there is anything problematic about the data representation or the decompression algorithm. The compression algorithm is another story, and it's not real well commented :-(. The important issues are how you search for matches in the past text and how you decide which match is the best one to use. Please update the code comments to describe that, and I'll take another look. regards, tom lane