Re: [HACKERS] pg_subscription_rel entry can be updated concurrently

2017-06-13 Thread Masahiko Sawada
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

Re: [HACKERS] pg_subscription_rel entry can be updated concurrently

2017-06-12 Thread Petr Jelinek
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

Re: [HACKERS] pg_subscription_rel entry can be updated concurrently

2017-06-12 Thread Michael Paquier
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

[HACKERS] pg_subscription_rel entry can be updated concurrently

2017-06-12 Thread Masahiko Sawada
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