pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jochem van Dieten <jochemd@oli.tudelft.nl>
To: pgsql-performance@postgresql.org
Subject: Re: planner/optimizer question
Date: Fri, 30 Apr 2004 19:46:24 +0200
Message-ID: <409290F0.10509@oli.tudelft.nl> (raw)
References: <pvc290584alms4s6hurvsh5ra09ki7se1s@email.aon.at>

Manfred Koizar wrote:
> On Wed, 28 Apr 2004 09:05:04 -0400, Tom Lane <tgl@sss.pgh.pa.us> 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





view thread (37+ messages)  latest in thread

Message-ID: <409290F0.10509@oli.tudelft.nl>
Permalink:  ../409290F0.10509@oli.tudelft.nl/
Also on:    postgresql.org/message-id/409290F0.10509@oli.tudelft.nl

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: jochemd@oli.tudelft.nl
  Subject: Re: planner/optimizer question
  In-Reply-To: <409290F0.10509@oli.tudelft.nl>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox