| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | SATYANARAYANA NARLAPURAM <satyanarlapuram(at)gmail(dot)com>, Ondřej Žižka <ondrej(dot)zizka(at)stratox(dot)cz>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Synchronous commit behavior during network outage |
| Date: | 2021-07-02 05:59:47 |
| Message-ID: | 3bb1eaa490dee98d85439ea70a094696f3b8d534.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2021-06-30 at 17:28 +0500, Andrey Borodin wrote:
> > My patch also covers the backend termination case. Is there a
> > reason
> > you left that case out?
>
> Yes, backend termination is used by HA tool before rewinding the
> node.
Can't you just disable sync rep first (using ALTER SYSTEM SET
synchronous_standby_names=''), which will unstick the backend, and then
terminate it?
If you don't handle the termination case, then there's still a chance
for the transaction to become visible to other clients before its
replicated.
> There is one more caveat we need to fix: we should prevent instant
> recovery from happening.
That can already be done with the restart_after_crash GUC.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-07-02 06:25:54 | Re: wrong relkind error messages |
| Previous Message | Jeff Davis | 2021-07-02 05:55:40 | Re: Replication protocol doc fix |