Re: BUG #9118: WAL Sender does not disconnect replication clients during shutdown
| От | Michael Paquier |
|---|---|
| Тема | Re: BUG #9118: WAL Sender does not disconnect replication clients during shutdown |
| Дата | |
| Msg-id | CAB7nPqTHTX7wDwF1=wTFto_1FQqTFjQDxe0uBrPdsAYvDpHYdA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #9118: WAL Sender does not disconnect replication clients during shutdown (Fujii Masao <masao.fujii@gmail.com>) |
| Ответы |
Re: BUG #9118: WAL Sender does not disconnect replication
clients during shutdown
|
| Список | pgsql-bugs |
On Fri, Mar 14, 2014 at 3:59 AM, Fujii Masao <masao.fujii@gmail.com> wrote: > On second thought, I think that it's better to check a write location instead > if walsender is connecting to a standby such as pg_receivexlog which > always returns an invalid flush location. Attached patch does this. Thought? Just a small one: could it be possible to put the condition checking for the validity of flush/write position into a separate variable out of this if() for readability? sentPtr == MyWalSnd->flush || ! (XLogRecPtrIsInvalid(MyWalSnd->flush) && ! sentPtr == MyWalSnd->write) Are there risks that a standby sends an invalid flush location and a valid write location? Regards, -- Michael
В списке pgsql-bugs по дате отправления: