Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
Дата
Msg-id 49932CFF.6090801@enterprisedb.com
обсуждение исходный текст
Ответ на Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
Список pgsql-hackers
Alvaro Herrera wrote:
> Tom Lane wrote:
>> Alvaro Herrera <alvherre@commandprompt.com> writes:
>>> Alvaro Herrera wrote:
>>>> ITAGAKI Takahiro wrote:
>>>>> 1. fillfactor.* options are silently ignored when the table doesn't have
>>>>> toast relation. Should we notice the behabior to users?
>>>>> ex. NOTICE: toast storage parameters are ignored
>>>> You mean "toast.* options"?  If so, yes, they are silently ignored.
>>>> Maybe issuing a warning is not a bad idea.  Care to propose a patch?
>>> Any takers here?
>> I tend to think this isn't a very good idea.  It's difficult for
>> applications to know whether a toast table will be created or not.
>> They should be able to just set the toast options and not worry.
> 
> The problem is where do we store the options?

How about in the reloptions of the main relation?

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,