Hi, I often get an error "ERROR: tuple concurrently updated" when changing subscription state(ALTER SUBSCRIPTION or DROP SUBSCRIPTION). The cause of this error is that table sync worker and apply worker can try to update the same tuple in pg_subscription_rel. Especially it often happens when we do initial copy for many tables and change it during executing.
I think that touching the same tuple by two worker processes happens when aborting replication for a table or a subscription, so it would be the same result as when the worker ends up with an error. But I think since it's not an appropriate behavior we should deal with it. Any thoughts? Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers