Re: make MaxBackends available in _PG_init
| От | Nathan Bossart |
|---|---|
| Тема | Re: make MaxBackends available in _PG_init |
| Дата | |
| Msg-id | 20220412194938.GA2064338@nathanxps13 обсуждение исходный текст |
| Ответ на | Re: make MaxBackends available in _PG_init (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: make MaxBackends available in _PG_init
|
| Список | pgsql-hackers |
On Tue, Apr 12, 2022 at 03:12:42PM -0400, Robert Haas wrote: > But if there's even one use case where adjusting GUCs at this phase is > reasonable, then 0003 isn't really good enough. We need an 0004 that > provides a new hook in a place where such changes can safely be made. I think that is doable. IMO it should be ѕomething like _PG_change_GUCs() that is called before _PG_init(). The other option is to add a hook called after _PG_init() where MaxBackends is available (in which case we likely want GetMaxBackends() again). Thoughts? > Meanwhile, committed 0001. Thanks. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: