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-14T04:26:57Z

Lists: pgsql-hackers

Attachments

0001-Add-repalloc0-and-repalloc0_array.patch (text/plain) patch 0001

I have another little idea that fits well here: repalloc0 and 
repalloc0_array.  These zero out the space added by repalloc.  This is a 
common pattern in the backend code that is quite hairy to code by hand. 
See attached patch.

Commits

Add repalloc0 and repalloc0_array
- b4b7ce8061d3 16.0 landed
Expand palloc/pg_malloc API for more type safety
- 2864f7755611 10.23 landed
- e962235fe1f6 11.18 landed
- 7dd9b469bc56 12.13 landed
- 172882292451 13.9 landed
- b7f37af7c195 14.6 landed
- 7fe55d5e12b6 15.0 landed
- 2016055a92f2 16.0 landed
Assorted examples of expanded type-safer palloc/pg_malloc API
- 5015e1e1b58f 16.0 landed