On Tue, Jun 13, 2017 at 2:55 PM, Petr Jelinek
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
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_s
On Tue, Jun 13, 2017 at 9:52 AM, 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
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 d