| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Nick Cleaton <nick(at)cleaton(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: streaming replication master can fail to shut down |
| Date: | 2016-04-29 03:38:18 |
| Message-ID: | 20160429033818.57elicwvviugfwyv@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2016-04-28 20:04:21 +0100, Nick Cleaton wrote:
> On 28 April 2016 at 19:14, Andres Freund <andres(at)anarazel(dot)de> wrote:
> >
> >> in this test the server sent only 29 keepalives during the shutdown:
> >> http://nick.cleaton.net/protodump-100k-nossl-patched.xz (47k)
> >
> > I guess you have a fair amount of WAL traffic, and the receiver was
> > behind a good bit?
>
> No, IIRC this was on the test cluster that I installed for the purpose
> of replicating the problem under 9.5; it was essentially idle.
The reason I'm asking is that I so far can't really replicate the issue
so far. It's pretty clear that waiting_for_ping_response = true; is
needed, but I'm suspicious that that's not all.
Was your standby on a separate machine? What kind of latency?
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick Cleaton | 2016-04-29 07:05:51 | Re: streaming replication master can fail to shut down |
| Previous Message | kayzizz | 2016-04-29 01:38:40 | BUG #14120: Documentation suggestion 35.4.2 |