| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unify drop-by-OID functions |
| Date: | 2020-05-02 08:01:54 |
| Message-ID: | 6ef08d3e-80d8-8731-ea82-bf0b63d040a3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-05-02 10:55:00 | Re: SLRU statistics |
| Previous Message | Fujii Masao | 2020-05-02 06:56:07 | Re: SLRU statistics |