Re: primary_conninfo missing from pg_stat_wal_receiver
От | Alvaro Herrera |
---|---|
Тема | Re: primary_conninfo missing from pg_stat_wal_receiver |
Дата | |
Msg-id | 20160630124148.GA236729@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: primary_conninfo missing from pg_stat_wal_receiver (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: primary_conninfo missing from pg_stat_wal_receiver
|
Список | pgsql-hackers |
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? -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: