| From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_subscription_rel entry can be updated concurrently |
| Date: | 2017-06-13 05:55:01 |
| Message-ID: | cc79942f-96d2-08ba-e29f-b7c23b4b77d7@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13/06/17 02:52, Masahiko Sawada 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?
>
This has been already reported by tushar in different thread and it's
still on my list to fix.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2017-06-13 06:08:10 | Re: pg_subscription_rel entry can be updated concurrently |
| Previous Message | Amit Langote | 2017-06-13 04:55:20 | Re: Dropping partitioned table drops a previously detached partition |