From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_subscription_rel entry can be updated concurrently |
Date: | 2017-06-13 06:08:10 |
Message-ID: | CAD21AoB-Kg0Z_-HzjPevAwWaS0y-ck3jm4QSBYSV-WwHLs43_g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jun 13, 2017 at 2:55 PM, Petr Jelinek
<petr(dot)jelinek(at)2ndquadrant(dot)com> wrote:
> 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.
>
Okay, I see. I added it to the open item list.
Regards,
--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-06-13 06:33:32 | pg_receivewal and messages printed in non-verbose mode |
Previous Message | Petr Jelinek | 2017-06-13 05:55:01 | Re: pg_subscription_rel entry can be updated concurrently |