Re: Revitalising VACUUM FULL for 8.3

Поиск
Список
Период
Сортировка
От Zeugswetter Andreas ADI SD
Тема Re: Revitalising VACUUM FULL for 8.3
Дата
Msg-id E1539E0ED7043848906A8FF995BDA57901CAFFCD@m0143.s-mxs.net
обсуждение исходный текст
Ответ на Re: Revitalising VACUUM FULL for 8.3  ("Simon Riggs" <simon@2ndquadrant.com>)
Ответы Re: Revitalising VACUUM FULL for 8.3  ("Simon Riggs" <simon@2ndquadrant.com>)
Список pgsql-hackers
>         -- start the VACUUM from the first non-filled block
>
> So if we do this, we wouldn't need to worry about HOT tuples
> at all, nor would we need to wait until all transactions are gone.

You need to wait until you are allowed to truncate if you want
concurrency.
Or a concurrent scan might miss a row, because the visible tuple got
truncated away.

Andreas


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

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Postgres Replication
Следующее
От: Hannu Krosing
Дата:
Сообщение: Re: Revitalising VACUUM FULL for 8.3