Re: primary_conninfo missing from pg_stat_wal_receiver
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, Stephen Frost <sfrost@snowman.net>, Tom Lane <tgl@sss.pgh.pa.us>, Tatsuo Ishii <ishii@postgresql.org>, Vik Fearing <vik@2ndquadrant.fr>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2016-06-30T13:12:33Z
Lists: pgsql-hackers
On Thu, Jun 30, 2016 at 9:41 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Fujii Masao wrote: >> On Thu, Jun 30, 2016 at 9:30 PM, Michael Paquier >> <michael.paquier@gmail.com> wrote: >> > On Thu, Jun 30, 2016 at 8:59 PM, Fujii Masao <masao.fujii@gmail.com> wrote: > >> >> ISTM that we will never be able to get out of this loop if walreceiver >> >> fails to connect to the master (e.g., password is wrong) after we enter >> >> this loop. >> > >> > Wouldn't it be cleaner to just return an error here instead of retrying? >> >> I prefer to return NULL. Now NULL is returned when walreceiver's pid is 0. >> We can just change this logic so that NULL is returned pid is 0 OR the >> flag is false. > > For the conninfo only, or for everything? All of them. If this connstr is not ready for display, the WAL receiver does not have a proper connection yet, so there is nothing worth showing anyway to the user. -- Michael
Commits
-
Add conninfo to pg_stat_wal_receiver
- 9ed551e0a4fd 9.6.0 landed
-
Only show pg_stat_replication details to superusers
- f88a638199d8 9.1.0 cited