From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Alter subscription..SET - NOTICE message is coming for table which is already removed |
Date: | 2017-06-03 05:04:26 |
Message-ID: | 20170603050426.GA1509839@rfd.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 31, 2017 at 10:15:50PM -0400, Peter Eisentraut wrote:
> 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.
The above-described topic is currently a PostgreSQL 10 open item. You own
this open item. Please observe the policy on open item ownership and send a
status update within three calendar days of this message. Include a date for
your subsequent status update.
From | Date | Subject | |
---|---|---|---|
Next Message | Noah Misch | 2017-06-03 05:12:46 | Re: walsender & parallelism |
Previous Message | Noah Misch | 2017-06-03 04:58:40 | Re: Server ignores contents of SASLInitialResponse |