Re: Unify drop-by-OID functions - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Unify drop-by-OID functions
Date
Msg-id a5f49f9f-a638-9f3a-7619-886f15115dc0@2ndquadrant.com
Whole thread Raw
In response to Re: Unify drop-by-OID functions  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 2020-05-05 18:05, Robert Haas wrote:
> This reminds me: I think that the issues in
> http://postgr.es/m/CA+TgmoYaFYRRdRZ94p_Qdt+1oONg6sMOvbkGHKVsFtONCrFkhw@mail.gmail.com
> should be considered here - we should guarantee that there's a
> snapshot registered continuously from before the call to
> SearchSysCache1 until after the call to CatalogTupleDelete. In the
> systable_beginscan case, we should be fine as long as the
> systable_endscan follows the CatalogTupleDelete call.

I considered this, but it seems independent of my patch.  If there are 
changes to be made, there are now fewer places to fix up.

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Unify drop-by-OID functions
Next
From: David Rowley
Date:
Subject: Re: Speedup usages of pg_*toa() functions