Re: Is custom MemoryContext prohibited?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Kohei KaiGai <kaigai(at)heterodb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is custom MemoryContext prohibited?
Date: 2020-02-05 14:19:04
Message-ID: CA+TgmoYTfOzi75yiM5PjDffNyfQ+rBdTWraCLhnkbt9JeaU2Zg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 28, 2020 at 9:54 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2020-02-05 14:28:08 Re: Is custom MemoryContext prohibited?
Previous Message Robert Haas 2020-02-05 14:15:46 Re: [Proposal] Global temporary tables