Re: Memory allocation abstraction in pgcrypto
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2020-09-23T07:57:44Z
Lists: pgsql-hackers
On Fri, Sep 18, 2020 at 10:00:04PM +0200, Daniel Gustafsson wrote: > The attached removes it in favor of using palloc() et.al directly. Is there > any reason to keep it around still? I doubt that anybody has been compiling with PX_OWN_ALLOC in the last years, so let's remove this abstraction. And +1 for your patch. -- Michael
Commits
-
Remove custom memory allocation layer in pgcrypto
- ca7f8e2b86e5 14.0 landed