Re: Unify drop-by-OID functions

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>, Ranier Vilela <ranier.vf@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-06-09T07:55:27Z
Lists: 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



Commits

  1. Unify drop-by-OID functions