From: Tom Lane <tgl@sss.pgh.pa.us>
To: Manfred Koizar <mkoi-pg@aon.at>
Cc: Gary Doades <gpd@gpdnet.co.uk>
Cc: pgsql-performance@postgresql.org
Subject: Re: planner/optimizer question
Date: Wed, 28 Apr 2004 09:05:04 -0400
Message-ID: <27806.1083157504@sss.pgh.pa.us> (raw)
In-Reply-To: <j8nu80566omg3pne8bs1qtco2s8aeggnnq@email.aon.at>
References: <20040426171103.45600.qmail@uno.mnl.com>
<23032.1083126479@sss.pgh.pa.us>
<408F5ECD.29849.CA91084@localhost>
<j8nu80566omg3pne8bs1qtco2s8aeggnnq@email.aon.at>
Manfred Koizar <mkoi-pg@aon.at> writes:
> On Wed, 28 Apr 2004 07:35:41 +0100, "Gary Doades" <gpd@gpdnet.co.uk>
> wrote:
>> Why is there an entry in the index for a row if the row is not valid?
> Because whether a row is seen as valid or not lies in the eye of the
> transaction looking at it. Full visibility information is stored in the
> heap tuple header. The developers' consensus is that this overhead
> should not be in every index tuple.
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.
regards, tom lane
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: tgl@sss.pgh.pa.us, mkoi-pg@aon.at, gpd@gpdnet.co.uk
Subject: Re: planner/optimizer question
In-Reply-To: <27806.1083157504@sss.pgh.pa.us>
* 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