Re: Expand palloc/pg_malloc API
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Expand palloc/pg_malloc API |
| Дата | |
| Msg-id | fecfcbc1-34ca-baaf-cde3-dc2d60830058@enterprisedb.com обсуждение |
| Ответ на | Re: Expand palloc/pg_malloc API (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Expand palloc/pg_malloc API
|
| Список | 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 по дате отправления: