| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-06-09 07:55:27 |
| Message-ID: | a5f49f9f-a638-9f3a-7619-886f15115dc0@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2020-06-09 08:07:23 | Re: Speedup usages of pg_*toa() functions |
| Previous Message | Peter Eisentraut | 2020-06-09 07:54:24 | Re: Unify drop-by-OID functions |