Re: Properly initialize negative/empty cache entries in relfilenodemap - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Properly initialize negative/empty cache entries in relfilenodemap
Date
Msg-id 20130829123809.GB5277@awork2.anarazel.de
Whole thread Raw
In response to Re: Properly initialize negative/empty cache entries in relfilenodemap  ("MauMau" <maumau307@gmail.com>)
List pgsql-hackers
On 2013-08-29 21:35:13 +0900, MauMau wrote:
> >Andres Freund wrote:
> >>Hi,
> >>
> >>Thanks to the valgrind instrumentation I found a small oversight in the
> >>relfilenodemap patch which is fixed in the attached patch.

> Great!  Could anybody find the root cause for the following memory leak
> problem, and if possible, fix this?

> http://www.postgresql.org/message-id/214653D8DF574BFEAA6ED53E545E99E4@maumau

> Heiki helped to solve this and found that pg_statistic entries are left in
> CacheMemoryContext, but we have no idea where and how they are created and
> left.  This seems difficult to me.

That doesn't have anything to do with this patch/feature though, has it?
For one, the feature has only been integrated into HEAD after you've
reported the issue, for another, it's not even active unless you use it
the first time.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: "MauMau"
Date:
Subject: Re: Properly initialize negative/empty cache entries in relfilenodemap
Next
From: Tom Lane
Date:
Subject: Re: [v9.4] row level security