Re: Allow ALTER SYSTEM SET on unrecognized custom GUCs

Поиск
Список
Период
Сортировка
От Andrei Lepikhov
Тема Re: Allow ALTER SYSTEM SET on unrecognized custom GUCs
Дата
Msg-id a539dd7b-fd35-47ee-8eeb-22ddae1b3e3a@postgrespro.ru
обсуждение исходный текст
Ответ на Re: Allow ALTER SYSTEM SET on unrecognized custom GUCs  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Allow ALTER SYSTEM SET on unrecognized custom GUCs  (shihao zhong <zhong950419@gmail.com>)
Список pgsql-hackers
On 18/10/2023 12:15, Tom Lane wrote:
> Andrei Lepikhov <a.lepikhov@postgrespro.ru> writes:
>> "SET foo.bar TO 'smth'" can immediately alter the placeholder's value.
>> But what is the reason that "ALTER SYSTEM SET foo.bar TO 'smth'" doesn't
>> do the same?
> 
> Because it's not supposed to take effect until you issue a reload
> command (and maybe not even then, depending on which GUC we're
> talking about).  I certainly think it wouldn't make sense for your
> own session to adopt the value ahead of others.

Thanks for the answer.
Introducing the assignable_custom_variable_name can be helpful. The code 
looks good. I think it deserves to be committed - after the indentation 
fix, of course.

-- 
regards,
Andrey Lepikhov
Postgres Professional




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

Предыдущее
От: Andrei Lepikhov
Дата:
Сообщение: Re: Asymmetric partition-wise JOIN
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written}