Re: [HACKERS] DROP SUBSCRIPTION, query cancellations and slothandling - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] DROP SUBSCRIPTION, query cancellations and slothandling
Date
Msg-id 93d814dd-1d41-28f5-5b68-dcc3469a25a1@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] DROP SUBSCRIPTION, query cancellations and slothandling  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: [HACKERS] DROP SUBSCRIPTION, query cancellations and slothandling  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
On 4/20/17 10:19, Petr Jelinek wrote:
> Hmm well since this only affects the synchronization of table
> states/names, I guess we could just simply do that before we create the
> slot as there is no expectancy of consistency between slot and the table
> list snapshot.

I suppose that wouldn't hurt.

Prior to the table sync patch, a missing target relation would just show
up as an error later on in the logs.  So having the error sooner
actually seems like a good change.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Removing select(2) based latch (was Unportable implementation of background worker start)
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Removing select(2) based latch (was Unportableimplementation of background worker start)