| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Expand palloc/pg_malloc API |
| Date: | 2022-05-24 14:03:27 |
| Message-ID: | fecfcbc1-34ca-baaf-cde3-dc2d60830058@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-05-24 14:10:36 | Re: Use Dblink without column defination |
| Previous Message | Jonathan S. Katz | 2022-05-24 13:33:14 | Re: PostgreSQL 15 Beta 1 release announcement draft |