Re: Re: Alter subscription..SET - NOTICE message is coming for table which is already removed

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Alter subscription..SET - NOTICE message is coming for table which is already removed
Date: 2017-06-01 02:15:50
Message-ID: 12cde2ca-d7bb-5f0f-4bd6-e7154af358a5@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/30/17 13:25, Masahiko Sawada wrote:
> I think this cause is that the relation status entry could be deleted
> by ALTER SUBSCRIPTION REFRESH before corresponding table sync worker
> starting. Attached patch fixes issues reported on this thread so far.

This looks like a reasonable change, but it conflicts with the change
discussed on "logical replication - still unstable after all these
months". I think I'll deal with that one first.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2017-06-01 02:18:46 Re: TAP: allow overriding PostgresNode in get_new_node
Previous Message Peter Eisentraut 2017-06-01 02:14:09 Re: logical replication - still unstable after all these months