Re: when the startup process doesn't
От | Jehan-Guillaume de Rorthais |
---|---|
Тема | Re: when the startup process doesn't |
Дата | |
Msg-id | 20210420171720.56599607@firost обсуждение исходный текст |
Ответ на | Re: when the startup process doesn't (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: when the startup process doesn't
|
Список | pgsql-hackers |
On Tue, 20 Apr 2021 15:04:28 +0200 Magnus Hagander <magnus@hagander.net> wrote: [...] > Yeah, I think we should definitely limit this to local access, one way > or another. Realistically using pg_hba is going to require catalog > access, isn't it? And we can't just go ignore those rows in pg_hba > that for example references role membership (as well as all those auth > methods you can't use). Two another options: 1. if this is limited to local access only, outside of the log entries, the status of the startup could be updated in the controldata file as well. This would allows to watch it without tail-grep'ing logs using eg. pg_controldata. 2. maybe the startup process could ignore update_process_title? As far as I understand the doc correctly, this GUC is mostly useful for backends on Windows. Regards,
В списке pgsql-hackers по дате отправления: