Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOAST table does not exist
Дата
Msg-id 6645.1516891210@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOASTtable does not exist  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOASTtable does not exist  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Re: [PATCH][PROPOSAL] Refuse setting toast.* reloptions when TOASTtable does not exist  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> On 1/23/18 13:39, Robert Haas wrote:
>> I don't understand.  AAUI, it is currently the case that if you set
>> the options before the TOAST table exists, they are lost.

> Well, that's also weird.

Well, maybe the right answer is to address that.  It's clear to me
why that would happen if we store these things as reloptions on the
toast table, but can't they be stored on the parent table?

Backward compatibility might be an issue, but I doubt that there
are enough people using these options that we couldn't get away
with breaking things, if we're unable to find a decent automatic
conversion method.

            regards, tom lane


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

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: reducing isolation tests runtime
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: [HACKERS] Vacuum: allow usage of more than 1GB of work mem