Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings
Дата
Msg-id 20080814012834.GG4672@alvh.no-ip.org
обсуждение исходный текст
Ответ на Re: autovacuum: use case for indenpedent TOAST table autovac settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-performance
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Does anyone see a need for having TOAST tables be individually
> > configurable for autovacuum?  I've finally come around to looking at
> > being able to use ALTER TABLE for autovacuum settings, and I'm wondering
> > if we need to support that case.
>
> It seems like we'll want to do it somehow.  Perhaps the cleanest way is
> to incorporate toast-table settings in the reloptions of the parent
> table.  Otherwise dump/reload is gonna be a mess.

Yeah, Magnus was suggesting this syntax:

ALTER TABLE foo SET toast_autovacuum_enable = false;
and the like.

My question is whether there is interest in actually having support for
this, or should we just inherit the settings from the main table.  My
gut feeling is that this may be needed in some cases, but perhaps I'm
overengineering the thing.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: autovacuum: use case for indenpedent TOAST table autovac settings
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings