Horton

Re: Expand palloc/pg_malloc API

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2022-09-12T06:53:53Z
Lists: pgsql-hackers 
On 09.09.22 22:13, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> I have updated this patch set to rename the _obj() functions to
>> _object(), and I have dropped the _ptrtype() variants.
> 
>> I have also split the patch to put the new API and the example uses into
>> separate patches.
> 
> This patch set seems fine to me, so I've marked it Ready for Committer.

committed

> 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.

Commits

  1. Add repalloc0 and repalloc0_array

  2. Expand palloc/pg_malloc API for more type safety

  3. Assorted examples of expanded type-safer palloc/pg_malloc API