Re: Expand palloc/pg_malloc API - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Expand palloc/pg_malloc API
Date
Msg-id 3ba19edb-9cfb-0173-f185-cb72cfc3829c@enterprisedb.com
Whole thread Raw
In response to Re: Expand palloc/pg_malloc API  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 12.09.22 15:49, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> On 09.09.22 22:13, Tom Lane wrote:
>>> I think serious consideration should be given to back-patching the
>>> 0001 part (that is, addition of the macros).  Otherwise we'll have
>>> to remember not to use these macros in code intended for back-patch,
>>> and that'll be mighty annoying once we are used to them.
> 
>> Yes, the 0001 patch is kept separate so that we can do that when we feel
>> the time is right.
> 
> I think the right time is now, or at least as soon as you're
> satisfied that the buildfarm is happy.

This has been done.




pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: A small typo
Next
From: Peter Eisentraut
Date:
Subject: Re: Expand palloc/pg_malloc API