| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Expand palloc/pg_malloc API |
| Date: | 2022-08-28 17:22:39 |
| Message-ID: | b45f210e-bc31-c800-e825-67e26f4afc08@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12.08.22 09:31, Peter Eisentraut wrote:
> In talloc, the talloc() function itself allocates an object of a given
> type. To allocate something of a specified size, you'd use
> talloc_size(). So those names won't map exactly. I'm fine with
> palloc_object() if that is clearer.
> I think the _ptrtype variant isn't that useful anyway, so if it's
> confusing we can leave it out.
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.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Expand-palloc-pg_malloc-API-for-more-type-safety.patch | text/plain | 3.8 KB |
| v2-0002-Assorted-examples-of-expanded-type-safer-palloc-p.patch | text/plain | 25.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2022-08-28 18:38:09 | Re: effective_multixact_freeze_max_age issue |
| Previous Message | Justin Pryzby | 2022-08-28 17:10:29 | Re: CI and test improvements |