X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 7BC4FD1B528 for ; Thu, 9 Oct 2003 20:33:13 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 23225-03 for ; Thu, 9 Oct 2003 17:32:26 -0300 (ADT) Received: from smtp.noos.fr (nan-smtp-11.noos.net [212.198.2.82]) by svr1.postgresql.org (Postfix) with ESMTP id 2EF04D1B4ED for ; Thu, 9 Oct 2003 17:32:24 -0300 (ADT) Received: (qmail 5276007 invoked by uid 0); 9 Oct 2003 20:32:24 -0000 Received: from unknown (HELO bigfoot.com) ([212.198.37.110]) (envelope-sender ) by 212.198.2.82 (qmail-ldap-1.03) with SMTP for ; 9 Oct 2003 20:32:24 -0000 Message-ID: <3F85A9B5.6030301@bigfoot.com> Date: Thu, 09 Oct 2003 20:32:21 +0200 From: Gaetano Mendola User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Cc: Greg Spiegelberg Subject: Re: Compare rows References: <3F841A28.8060504@cranel.com> <200310081010.26576.josh@agliodbs.com> <3F84613D.8040207@cranel.com> <200310081611.59179.josh@agliodbs.com> <3F857E1C.1040209@cranel.com> In-Reply-To: <3F857E1C.1040209@cranel.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/310 X-Sequence-Number: 4058 Greg Spiegelberg wrote: > Josh Berkus wrote: > >> >> As you can see, the NULLs are not stored, making this system much more >> efficient on storage space. >> >> Tommorrow I'll (hopefully) write up how to query this for >> comparisons. It would help if you gave a little more details about >> what specific comparison you're doing, e.g. between tables or table to >> value, comparing just the last value or all rows, etc. >> > > Got it. I can see how it would be more efficient in storing. At this > point it would require a lot of query and code rewrites to handle it. > Fortunately, we're looking for alternatives for the next revision and > we're leaving ourselves open for a rewrite much to the boss's chagrin. I'm not sure about the save in storage. See the Hannu Krosing arguments. Regards Gaetano Mendola