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

From Tom Lane
Subject Re: Expand palloc/pg_malloc API
Date
Msg-id 1607236.1662990573@sss.pgh.pa.us
Whole thread Raw
In response to Re: Expand palloc/pg_malloc API  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: Expand palloc/pg_malloc API
List pgsql-hackers
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.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: pg_stat_statements locking
Next
From: Erik Rijkers
Date:
Subject: Re: proposal: possibility to read dumped table's name from file