Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> On 17.06.22 07:11, Tom Lane wrote:
>> Notably, I think the choice
>> that pfree(NULL) is disallowed traces directly to worries about
>> coding-pattern-compatibility with pre-POSIX free(). Should we
>> revisit that?
> Yes please, and also repalloc().
repalloc no, because you wouldn't know which context to do the
allocation in.
regards, tom lane