Re: Avoiding second heap scan in VACUUM

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: Avoiding second heap scan in VACUUM
Дата
Msg-id 2e78013d0805300220r77f88576u55b510159ee54b60@mail.gmail.com
обсуждение исходный текст
Ответ на Avoiding second heap scan in VACUUM  ("Pavan Deolasee" <pavan.deolasee@gmail.com>)
Ответы Re: Avoiding second heap scan in VACUUM  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-hackers
On Fri, May 30, 2008 at 2:41 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>
>  What I still
> don't accept is that an unconstrained wait is justifiable. You've just
> said its a minor detail, but that's not the way I see it. It might be a
> second, but it might be an hour or more.
>

I am suggesting a timed wait. May be say between 60-300 seconds.
That's the maximum VACUUM would get delayed. If exiting transactions
don't finish within that time, VACUUM just works as it does today. So
it can't certainly be much worse than what it is today.

> A non-waiting solution seems like the only way to proceed.
>

Yeah, but we don't have a simple solution yet which would work in all
cases and is not too complicated.

> Is this a non-issue anyway, with DSM?
>

I thought about that. DSM would certainly reduce the cost of heap
scans. But still the second pass would be required and it would
re-dirty all the pages again,

Thanks,
Pavan


-- 
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Radek Strnad
Дата:
Сообщение: Re: Proposal - Collation at database level
Следующее
От: "Pavan Deolasee"
Дата:
Сообщение: Re: Avoiding second heap scan in VACUUM