Re: Change pfree to accept NULL argument

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Change pfree to accept NULL argument
Date: 2022-08-28 08:00:34
Message-ID: 0c2d9164-a0ac-1a14-c837-110d05219e3a@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.08.22 20:30, Tom Lane wrote:
> I'm not very convinced that the benefits of making pfree() more
> like free() are worth those costs.
>
> We could ameliorate the first objection if we wanted to back-patch
> 0002, I guess.
>
> (FWIW, no objection to your 0001. 0004 and 0005 seem okay too;
> they don't touch enough places to create much back-patching risk.)

To conclude this, I have committed those secondary patches and updated
the utils/mmgr/README with some information from this discussion.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-08-28 11:04:21 Re: Reducing the chunk header sizes on all memory context types
Previous Message Michael Paquier 2022-08-28 07:23:08 Re: [PATCH] Add native windows on arm64 support