Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4) - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)
Date
Msg-id 50ED58AD.7050308@vmware.com
Whole thread Raw
In response to [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)
List pgsql-hackers
Tree view 
On 09.01.2013 13:27, Andres Freund wrote:
> - makes palloc() into a real function so CurrentMemoryContext doesn't
>    need to be provided

I don't understand the need for this change. Can't you just:

#define palloc(s) pg_malloc(s)

in the frontend context?

- Heikki

pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: ALTER command reworks
Next
From: Simon Riggs
Date:
Subject: Re: Further pg_upgrade analysis for many tables