| From: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Unify drop-by-OID functions |
| Date: | 2020-05-02 13:04:55 |
| Message-ID: | CAEudQAq1GBUFC=Xd5i+wzm8GCHivv8p1jB8GvpFOm=nJpWg2bQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Em sáb., 2 de mai. de 2020 às 05:01, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> escreveu:
> 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"?
>
Well, that's what I deduced from the cacheId variable name.
regards,
Ranier Vilela
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-05-02 14:05:29 | Re: pg_stat_reset_slru(name) doesn't seem to work as documented |
| Previous Message | Tomas Vondra | 2020-05-02 12:27:33 | Re: pg_stat_reset_slru(name) doesn't seem to work as documented |