On Thu, May 25, 2017 at 01:59:51PM +0530, tushar wrote: > After applying all your patches, drop subscription no more hangs while > dropping subscription but there is an error "ERROR: tuple concurrently > updated" in the log file of > standby. > > --- > logical replication synchronization worker finished processing > 2017-05-25 09:15:52.654 BST [18575] LOG: logical replication > synchronization worker finished processing > 2017-05-25 09:15:52.656 BST [18563] LOG: starting logical replication > worker for subscription "sub" > 2017-05-25 09:15:52.662 BST [18577] LOG: logical replication sync for > subscription sub, table t14 started > 2017-05-25 09:15:53.657 BST [18563] LOG: starting logical replication > worker for subscription "sub" > 2017-05-25 09:15:53.663 BST [18579] LOG: logical replication sync for > subscription sub, table t15 started > 2017-05-25 09:15:53.724 BST [18563] FATAL: terminating logical replication > worker due to administrator command > 2017-05-25 09:15:53.725 BST [18521] LOG: worker process: logical > replication worker for subscription 16684 (PID 18563) exited with exit code > 1 > 2017-05-25 09:15:54.734 BST [18579] ERROR: tuple concurrently updated > 2017-05-25 09:15:54.735 BST [18577] ERROR: tuple concurrently updated > 2017-05-25 09:15:54.736 BST [18521] LOG: worker process: logical > replication worker for subscription 16684 sync 16426 (PID 18579) exited with > exit code 1 > 2017-05-25 09:15:54.736 BST [18521] LOG: worker process: logical > replication worker for subscription 16684 sync 16423 (PID 18577) exited with > exit code 1 > ~ > ~ > ~ > > Steps to reproduce - > X cluster -> create 100 tables , publish all tables (create publication pub > for all tables); > Y Cluster -> create 100 tables ,create subscription(create subscription sub > connection 'user=centos host=localhost' publication pub; > Y cluster ->drop subscription - drop subscription sub; > > check the log file on Y cluster. > > Sometime , i have seen this error on psql prompt and drop subscription > operation got failed at first attempt. > > postgres=# drop subscription sub; > ERROR: tuple concurrently updated > postgres=# drop subscription sub; > NOTICE: dropped replication slot "sub" on publisher > DROP SUBSCRIPTION
[Action required within three days. This is a generic notification.] The above-described topic is currently a PostgreSQL 10 open item. Peter, since you committed the patch believed to have created it, you own this open item. If some other commit is more relevant or if this does not belong as a v10 open item, please let us know. Otherwise, please observe the policy on open item ownership[1] and send a status update within three calendar days of this message. Include a date for your subsequent status update. Testers may discover new open items at any time, and I want to plan to get them all fixed well in advance of shipping v10. Consequently, I will appreciate your efforts toward speedy resolution. Thanks. [1] https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
