Skip site navigation (1) Skip section navigation (2)

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

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)
Date: 2013-01-09 11:46:53
Message-ID: 50ED58AD.7050308@vmware.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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


In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2013-01-09 11:55:18
Subject: Re: Further pg_upgrade analysis for many tables
Previous:From: Kohei KaiGaiDate: 2013-01-09 11:46:37
Subject: Re: ALTER command reworks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group