Re: Disallow cancellation of waiting for synchronous replication
От | Robert Haas |
---|---|
Тема | Re: Disallow cancellation of waiting for synchronous replication |
Дата | |
Msg-id | CA+TgmoaCBwgMDkeBDOgtPgHcbfSYq+zORjL5DoU3pJyjALxtoQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Disallow cancellation of waiting for synchronous replication (Maksim Milyutin <milyutinma@gmail.com>) |
Ответы |
Re: Disallow cancellation of waiting for synchronous replication
|
Список | 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 по дате отправления: