Re: list append syntax for postgresql.conf

Поиск
Список
Период
Сортировка
Искать
От
Chapman Flack
Тема
Re: list append syntax for postgresql.conf
Дата
Msg-id
5d7f20e3-aa67-cf7c-2996-0f2a58250ee1@anastigmatix.net
Ответ на
Список
Дерево обсуждения
list append syntax for postgresql.conf Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: list append syntax for postgresql.conf Tom Lane <tgl@sss.pgh.pa.us>
Re: list append syntax for postgresql.conf Christoph Berg <myon@debian.org>
Re: list append syntax for postgresql.conf Joe Conway <mail@joeconway.com>
Re: list append syntax for postgresql.conf Chapman Flack <chap@anastigmatix.net>
Re: list append syntax for postgresql.conf Robert Haas <robertmhaas@gmail.com>
Re: list append syntax for postgresql.conf Tom Lane <tgl@sss.pgh.pa.us>
Re: list append syntax for postgresql.conf Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Re: list append syntax for postgresql.conf Euler Taveira <euler@timbira.com.br>
Re: list append syntax for postgresql.conf "David G. Johnston" <david.g.johnston@gmail.com>
On 2/20/19 10:54 AM, Joe Conway wrote:
>>     shared_preload_libraries += 'pg_stat_statements'
> 
> I like the idea, but presume it would apply to any GUC list, not just
> shared_preload_libraries?

It would be nice if there were some way for extensions to declare
GUC lists (the very thing that recently became explicitly unsupported).

The difficulty seems to be that a GUC may be assigned before the
extension has been loaded to determine whether list syntax should apply.

Could a change like this improve that situation too, perhaps by
deciding that += syntax /implies/ that an as-yet-undeclared GUC is
to be of list form (which could then be checked when the extension
declares the GUC)?

-Chap

В списке pgsql-hackers по дате отправления
От: Robert Haas
Дата:
От: Tom Lane
Дата:
FAQ