Re: planner/optimizer question

Поиск
Список
Период
Сортировка
Искать
От
Rod Taylor
Тема
Re: planner/optimizer question
Дата
Msg-id
1083265934.30065.359.camel@jester
Ответ на
Список
Дерево обсуждения
Re: planner/optimizer question Jochem van Dieten <jochemd@oli.tudelft.nl>
Re: planner/optimizer question Manfred Koizar <mkoi-pg@aon.at>
Re: planner/optimizer question Tom Lane <tgl@sss.pgh.pa.us>
Re: planner/optimizer question Jochem van Dieten <jochemd@oli.tudelft.nl>
Re: planner/optimizer question Tom Lane <tgl@sss.pgh.pa.us>
Re: planner/optimizer question "Gary Doades" <gpd@gpdnet.co.uk>
Re: planner/optimizer question Manfred Koizar <mkoi-pg@aon.at>
Re: planner/optimizer question "Jochem van Dieten" <jochemd@oli.tudelft.nl>
> 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 по дате отправления
От: Josh Berkus
Дата:
От: Gary Doades
Дата:
Сообщение: Re: planner/optimizer question
FAQ