Re: Get stuck when dropping a subscription during synchronizing table
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Petr Jelinek <petr.jelinek@2ndquadrant.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-05-11T07:06:15Z
Lists: pgsql-hackers
On Wed, May 10, 2017 at 11:57 AM, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > Barring any objections, I'll add these two issues to open item. It seems to me that those open items have not been added yet to the list. If I am following correctly, they could be defined as follows: - Dropping subscription may stuck if done during tablesync. -- Analyze deadlock issues with DROP SUBSCRIPTION and apply worker process. -- Avoid orphaned tablesync worker if apply worker exits before changing its status. I am playing with the code to look at both of them... But feel free to update this thread if I don't show up. There are no test cases, but some well-placed pg_usleep calls should make both issues easily reproducible. I have the gut feeling that other things are hidden behind though. -- Michael
Commits
-
Fix violations of CatalogTupleInsert/Update/Delete abstraction.
- a571c7f661a7 10.0 cited
-
Use standard interrupt handling in logical replication launcher.
- 2c48f5db64b1 10.0 landed
-
Make tablesync worker exit when apply dies while it was waiting for it
- 3c9bc2157a4f 10.0 cited
-
Use weaker locks when updating pg_subscription_rel
- 521fd4795e3e 10.0 cited