Re: Memory leak in vac_update_relstats ?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Memory leak in vac_update_relstats ?
Date: 2007-07-20 20:33:58
Message-ID: 46A11C36.1010205@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> I've actually thought about making short-term memory
> contexts use a variant MemoryContext type in which pfree was a no-op and
> palloc was simplified by not worrying at all about recycling space.
>
>
>

That sounds like a good idea to me.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2007-07-20 21:01:29 Re: CREATE TABLE LIKE INCLUDING INDEXES support
Previous Message Tom Lane 2007-07-20 20:24:01 Re: Memory leak in vac_update_relstats ?