Re: [PATCH] Introduce unified support for composite GUC options
| От | David G. Johnston |
|---|---|
| Тема | Re: [PATCH] Introduce unified support for composite GUC options |
| Дата | |
| Msg-id | CAKFQuwYJmBanaiU3VPMfSE+b8CfKeMMfGFXd9npKMMmbA7oiaw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] Introduce unified support for composite GUC options (Чумак Антон <a.chumak@postgrespro.ru>) |
| Ответы |
Re: [PATCH] Introduce unified support for composite GUC options
|
| Список | pgsql-hackers |
On Mon, Sep 22, 2025 at 10:33 PM Чумак Антон <a.chumak@postgrespro.ru> wrote:
Working with parameters is not limited to working within a session, otherwise the PGC_INTERNAL, PGC_POSTMASTER, and PGC_SIGHUP contexts would not be needed. My patch provides unified support for composite types and within such contexts. Example: you have a composite boot value and in the postgresql.conf file you need to change only 2 fields, and you need to do this at the same time to maintain the consistency of the structure. Now you would have to describe all the fields in one big line, and with the patch you can only describe the changed fields.
You might wish to try an approach where people who do think such a thing might be useful can voice their support for it rather than trying to convince people who don't presently see any immediate use cases that there are some (without saying what those use cases are...).
In short - post to -general.
As you note - moving runtime checks to "SET" time has value and this patch brings that value. But it is not evident there is enough value to take on the added complexity. There are few to no requests asking for this ability.
David J.
В списке pgsql-hackers по дате отправления: