From: Rod Taylor <pg@rbt.ca>
To: Gary Doades <gpd@gpdnet.co.uk>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: planner/optimizer question
Date: Thu, 29 Apr 2004 15:12:15 -0400
Message-ID: <1083265934.30065.359.camel@jester> (raw)
In-Reply-To: <409153EF.24647.144E9BF7@localhost>
References: <27806.1083157504@sss.pgh.pa.us>
<409153EF.24647.144E9BF7@localhost>
> I would be nice to get a feel for how much performance loss would be incurred in
> maintaining the index flags against possible performance gains for getting the data back
> out again.
I guess the real question is, why maintain index flags and not simply
drop the index entry altogether?
A more interesting case would be to have the backend process record
index tuples that it would invalidate (if committed), then on commit
send that list to a garbage collection process.
It's still vacuum -- just the reaction time for it would be much
quicker.
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: pg@rbt.ca, gpd@gpdnet.co.uk
Subject: Re: planner/optimizer question
In-Reply-To: <1083265934.30065.359.camel@jester>
* 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