On Thu, Jun 15, 2017 at 11:40:52PM -0400, Peter Eisentraut wrote: > On 6/13/17 15:49, Peter Eisentraut wrote: > > On 6/13/17 02:33, Noah Misch wrote: > >>> 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.] > > > > It's being worked on. Let's see by Thursday. > > A patch has been posted, and it's being reviewed. Next update Monday.
This PostgreSQL 10 open item is past due for your status update. Kindly send a status update within 24 hours, and include a date for your subsequent status update. Refer to the policy on open item ownership: 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
