On Tue, Jun 13, 2017 at 9:52 AM, Masahiko Sawada <sawada.m...@gmail.com> wrote: > 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?
Yes, this error is normally not be something that users should see. So there is something weird around the locking of the parent objects or in the way the catalog is updated. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
