Re: planner/optimizer question - Mailing list pgsql-performance

From Rod Taylor
Subject Re: planner/optimizer question
Date
Msg-id 1083265934.30065.359.camel@jester
Whole thread Raw
In response to Re: planner/optimizer question  ("Gary Doades" <gpd@gpdnet.co.uk>)
Responses Re: planner/optimizer question
List pgsql-performance
> 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.



pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Wierd context-switching issue on Xeon
Next
From: "Gary Doades"
Date:
Subject: Re: planner/optimizer question