Re: ps command does not show walsender's connected db
От | Bharath Rupireddy |
---|---|
Тема | Re: ps command does not show walsender's connected db |
Дата | |
Msg-id | CALj2ACWnRDbazJPDa_O33Bec6f04bVzOzpNiXKJBj0oNCY7BxA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: ps command does not show walsender's connected db (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: ps command does not show walsender's connected db
|
Список | pgsql-hackers |
On Tue, Nov 22, 2022 at 6:14 AM Michael Paquier <michael@paquier.xyz> wrote: > > On Thu, Nov 17, 2022 at 01:32:11PM +0900, Ian Lawrence Barwick wrote: > > Fujii-san is marked as committer on the commifest entry for this patch [1]; > > are you able to go ahead and get it committed? > > That's the state of the patch since the 11th of October. Seeing the > lack of activity, I propose to take care of that myself if there are > no objections, only on HEAD. That could be qualified as a bug, but > that does not seem worth bothering the back-branches, either. Except > if somebody has a different opinion? -1 for back-patching as it's not something critical to any of the server's operations. > The patch looks to do the job correctly, still I would leave the extra > printf() calls in BackendStartup() out. Are you looking at the latest v3 patch https://www.postgresql.org/message-id/4b5691462b994c18ff370aaa84cef0d0%40oss.nttdata.com? It has no printf() calls. -- Bharath Rupireddy PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: