On Wed, Mar 13, 2019 at 1:38 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> A bit, yes, but not overly so, and it's less fragile that not having
> such a protection. Anything that allocates in CacheMemoryContext needs
> to be very careful anyway.
True, but I think it's more fragile than either of the options I proposed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company