Re: palloc0

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: mohsen soodkhah mohammadi <mohsensoodkhah(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: palloc0
Date: 2013-12-01 05:46:55
Message-ID: CAB7nPqSex6dNsM04DLUxjOvMW9tRNfmbarJ01VEP8it_BGRcCQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Nov 30, 2013 at 11:41 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> Please read src/backend/utils/mmgr/README
And that as well directly in the docs:
http://www.postgresql.org/docs/devel/static/xfunc-c.html#AEN53984
"The memory allocated by palloc will be freed automatically at the end
of each transaction, preventing memory leaks."
Regards,
--
Michael

In response to

  • Re: palloc0 at 2013-11-30 14:41:27 from Andrew Dunstan

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2013-12-01 07:15:51 Re: Extension Templates S03E11
Previous Message Pavel Stehule 2013-12-01 04:50:42 Re: lock on object is already held