Consistently use palloc_object() and palloc_array()

David Geier <geidav.pg@gmail.com>

From: David Geier <geidav.pg@gmail.com>

To: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2025-11-26T22:09:31Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

btree_gist: Fix memory allocation formula
- 5cf03552fbb4 19 (unreleased) landed
Use palloc_object() and palloc_array(), the last change
- 4f7dacc5b82a 19 (unreleased) landed
pg_buffercache: Fix memory allocation formula
- 580b5c2f397f 18.2 landed
- 3f83de20ba2e 19 (unreleased) landed
Fix allocation formula in llvmjit_expr.c
- 0c67dbcc4e39 14.21 landed
- 07ddf6197b78 15.16 landed
- 5a4dc4aabd03 16.12 landed
- 0bab0c3b74af 17.8 landed
- 5b7bbf16db34 18.2 landed
- 06761b6096b6 19 (unreleased) landed
Use palloc_object() and palloc_array() in backend code
- 1b105f9472bd 19 (unreleased) landed
Use palloc_object() and palloc_array() in more areas of the tree
- 0c3c5c3b06a3 19 (unreleased) landed
Use more palloc_object() and palloc_array() in contrib/
- 31d3847a37be 19 (unreleased) landed

Attachments

v1-0001-Consistently-use-palloc_object-and-palloc_array.patch (text/x-patch) patch v1-0001

Hi hackers,

I've changed all code to use the "new" palloc_object(), palloc_array(),
palloc0_object(), palloc0_array, repalloc_array() and repalloc0_array()
macros. This makes the code more readable and more consistent.

The patch is pretty big but potential merge conflicts should be easy to
resolve. If preferred, I can also further split up the patch, e.g.
directory by directory or high impact files first.

The patch is passing "meson test" and I've additionally wrote a script
that parses the patch file and verifies that every two corresponding +
and - lines match (e.g. palloc0() replaced by palloc0_array() or
palloc0_object(), the same for palloc() and repalloc(), additionally
some checks to make sure the conversion to the _array() variant is
correct).

--
David Geier