Re: Disallow cancellation of waiting for synchronous replication - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Disallow cancellation of waiting for synchronous replication
Date
Msg-id CA+TgmoaCBwgMDkeBDOgtPgHcbfSYq+zORjL5DoU3pJyjALxtoQ@mail.gmail.com
Whole thread Raw
In response to Re: Disallow cancellation of waiting for synchronous replication  (Maksim Milyutin <milyutinma@gmail.com>)
Responses Re: Disallow cancellation of waiting for synchronous replication  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers
On Sat, Dec 28, 2019 at 6:19 PM Maksim Milyutin <milyutinma@gmail.com> wrote:
> The stuckness of backend is not deadlock here. To cancel waiting of
> backend fluently, client is enough to turn off synchronous replication
> (change synchronous_standby_names through server reload) or change
> synchronous replica to another livable one (again through changing of
> synchronous_standby_names). In first case he explicitly agrees with
> existence of local (not replicated) commits in master.

Sure, that's true. But I still maintain that responding to ^C is an
important property of the system. If you have to do some more
complicated set of steps like the ones you propose here, a decent
number of people aren't going to figure it out and will end up
unhappy. Now, as it is, you're unhappy, so I guess you can't please
everyone, but you asked for opinions so I'm giving you mine.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: xact_start for walsender & logical decoding not updated
Next
From: Robert Haas
Date:
Subject: Re: Building infrastructure for B-Tree deduplication that recognizeswhen opclass equality is also equivalence