Re: Is custom MemoryContext prohibited? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Is custom MemoryContext prohibited?
Date
Msg-id CA+TgmoYTfOzi75yiM5PjDffNyfQ+rBdTWraCLhnkbt9JeaU2Zg@mail.gmail.com
Whole thread Raw
In response to Re: Is custom MemoryContext prohibited?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Is custom MemoryContext prohibited?
List pgsql-hackers
On Tue, Jan 28, 2020 at 9:54 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Interesting.  But I bet there are platform and version dependencies
> in the mix, too.  I'd still not wish to rely on this for debugging.

Hmm.  What if we put a "const char *name" in the methods array? Then
even if you couldn't print out the function pointers, you would at
least see the name.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [Proposal] Global temporary tables
Next
From: Robert Haas
Date:
Subject: Re: Is custom MemoryContext prohibited?