X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id CA57ED1E8CB for ; Fri, 30 Apr 2004 14:46:45 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 85733-05 for ; Fri, 30 Apr 2004 14:46:24 -0300 (ADT) Received: from mailhost2.tudelft.nl (mailhost2.tudelft.nl [130.161.180.2]) by svr1.postgresql.org (Postfix) with ESMTP id A0534D1BABD for ; Fri, 30 Apr 2004 14:46:22 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by rav.antivirus (Postfix) with ESMTP id C640D17D93 for ; Fri, 30 Apr 2004 19:46:22 +0200 (MEST) Received: from listserv.tudelft.nl (listserv.tudelft.nl [130.161.180.33]) by mailhost2.tudelft.nl (Postfix) with ESMTP id A8C7017D8F for ; Fri, 30 Apr 2004 19:46:22 +0200 (MEST) Received: from oli.tudelft.nl (jochemd.tnw-s.tudelft.nl [145.94.90.156]) by listserv.tudelft.nl (8.12.10/8.12.8) with ESMTP id i3UHkMF7011958 for ; Fri, 30 Apr 2004 19:46:22 +0200 (MEST) Message-ID: <409290F0.10509@oli.tudelft.nl> Date: Fri, 30 Apr 2004 19:46:24 +0200 From: Jochem van Dieten Organization: OnLine Internet User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: planner/optimizer question References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at tudelft.nl X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/526 X-Sequence-Number: 6826 Manfred Koizar wrote: > On Wed, 28 Apr 2004 09:05:04 -0400, Tom Lane wrote: >>> [ ... visibility information in index tuples ... ] >> >> Storing that information would at least double the overhead space used >> for each index tuple. The resulting index bloat would significantly >> slow index operations by requiring more I/O. So it's far from clear >> that this would be a win, even for those who care only about select >> speed. > > While the storage overhead could be reduced to 1 bit (not a joke) You mean adding an isLossy bit and only where it is set the head tuple has to be checked for visibility, if it is not set the head tuple does not have to be checked? > we'd > still have the I/O overhead of locating and updating index tuples for > every heap tuple deleted/updated. Would there be additional I/O for the additional bit in the index tuple (I am unable to find the layout of index tuple headers in the docs)? Jochem -- I don't get it immigrants don't work and steal our jobs - Loesje