| From: | Evgeniy Efimkin <efimkin(at)yandex-team(dot)ru> |
|---|---|
| To: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15617: walsender hang if sync replica disconnected from network |
| Date: | 2019-03-08 18:00:04 |
| Message-ID: | 1117411552068004@sas2-76706d252d16.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi!
Maybe need additional diagnostic?
02.02.2019, 20:41, "Evgeniy Efimkin" <efimkin(at)yandex-team(dot)ru>:
> Hi!
> I reproduced it.
> 1. Make some write load on master: `pgbench -i -s 100000 testdb`
> 2. On sync replica drop output connections, while pgbench init database: `ip6tables -A OUTPUT -p tcp --dport 5432 -j DROP`
> 3. Until was_sender_timeout reached, i send SIGHUB on master: `select pg_reload_conf();`
> After that walsender forever stay in WaitEventSetWait, because no timeout
>
> src/backend/libpq/be-secure.c:273
> WaitEventSetWait(FeBeWaitSet, -1 /* no timeout */ , &event, 1,
> WAIT_EVENT_CLIENT_READ);
--------
Efimkin Evgeny
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-03-08 18:13:30 | Re: BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation) |
| Previous Message | PG Bug reporting form | 2019-03-08 17:38:33 | BUG #15678: The postgresql.conf string does not define server behavior (default_transaction_isolation) |