Re: walsender waiting_for_ping spuriously set
От | Alvaro Herrera |
---|---|
Тема | Re: walsender waiting_for_ping spuriously set |
Дата | |
Msg-id | 20200807231829.GA3040@alvherre.pgsql обсуждение исходный текст |
Ответ на | Re: walsender waiting_for_ping spuriously set (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: walsender waiting_for_ping spuriously set
|
Список | pgsql-hackers |
On 2020-Aug-07, Alvaro Herrera wrote: > I'm thinking in keeping the sentences that were added in that commit, > maybe like so: > > > * We only send regular messages to the client for full decoded > > * transactions, but a synchronous replication and walsender shutdown > > * possibly are waiting for a later location. So, before sleeping, we > > + * send a ping containing the flush location. A reply from standby is > > + * not needed and would be wasteful most of the time, > > + * but if the receiver is otherwise idle and walreceiver status messages > > + * are enabled, this keepalive will trigger a reply. Processing the > > + * reply will update these MyWalSnd locations. After rereading this a few more times, I think it's OK as Noah had it, so I'll just use his wording. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: