Re: handling TOAST tables in autovacuum

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: handling TOAST tables in autovacuum
Дата
Msg-id 25296.1212971005@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: handling TOAST tables in autovacuum  (Alvaro Herrera <alvherre@commandprompt.com>)
Список pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> The point here is that if the user disables autovac for the main table,
> then it's expected that it is automagically disabled for the toast table
> as well, for the usual case where they are disabling it because the
> table is too big.

Hmm, good point.  OK, two passes it is.  (I thought about remembering
the toast table rows in memory so as not to scan the catalog twice,
but I'm not sure you really save much that way.)

Another thing to think about here is locking: I believe you need to get
a vacuum-type lock on the parent table not only the toast table, so
vacuuming a toast table without any knowledge of which table is its
parent ain't gonna fly anyway.
        regards, tom lane


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: handling TOAST tables in autovacuum
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: libpq support for arrays and composites