Re: Unify drop-by-OID functions

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

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Ranier Vilela <ranier.vf@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-05-02T08:01:54Z
Lists: pgsql-hackers
On 2020-05-01 23:31, Ranier Vilela wrote:
> I can suggest improvements?
> 
> 1. In case Object is cached, delay open_table until the last moment, for 
> the row to be blocked as little as possible and close the table as 
> quickly as possible.
> 2. In case Object is cached and the tuple is invalid, do not open table.
> 3. Otherwise, is it possible to call systable_endscan, after table_close?

What do you mean by "object is cached"?

In any case, this is a refactoring patch, so significant changes to the 
internal logic would not really be in scope.

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



Commits

  1. Unify drop-by-OID functions