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

From Peter Eisentraut
Subject Re: Expand palloc/pg_malloc API
Date
Msg-id fecfcbc1-34ca-baaf-cde3-dc2d60830058@enterprisedb.com
Whole thread Raw
In response to Re: Expand palloc/pg_malloc API  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Expand palloc/pg_malloc API
List pgsql-hackers
On 17.05.22 20:43, Tom Lane wrote:
> So I think Peter's got a good idea here (I might quibble with the details
> of some of these macros).  But it's not really going to move the
> safety goalposts very far unless we make a concerted effort to make
> these be the style everywhere.  Are we willing to do that?  What
> will it do to back-patching difficulty?  Dare I suggest back-patching
> these changes?

I think it could go like the castNode() introduction: first we adopt it 
sporadically for new code, then we change over some larger pieces of 
code, then we backpatch the API, then someone sends in a big patch to 
change the rest.



pgsql-hackers by date:

Previous
From: "Jonathan S. Katz"
Date:
Subject: Re: PostgreSQL 15 Beta 1 release announcement draft
Next
From: Peter Eisentraut
Date:
Subject: Re: Use Dblink without column defination