Message-ID: <4B899EFD.90200@postnewspapers.com.au>
Date: Sun, 28 Feb 2010 06:38:53 +0800
From: Craig Ringer <craig@postnewspapers.com.au>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB;
	rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: Chris <ctlajoie@gmail.com>
CC: pgsql-performance@postgresql.org
Subject: Re: How to troubleshoot high mem usage by postgres?
References: <57033cf81002271429wb0da13am37b3cb6258103ea5@mail.gmail.com>
In-Reply-To: <57033cf81002271429wb0da13am37b3cb6258103ea5@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 28/02/2010 6:29 AM, Chris wrote:

> If I am indeed doing everything I can to release the resources (and
> I'm 95% sure I am) then it looks like the pgsql extension is at fault
> here.

Before assuming some particular thing is at fault, you need to collect 
some information to determine what is actually happening.

What are your queries?

What are the resource-releasing functions you're using, and how?

Can you boil this down to a simple PHP test-case that connects to a 
dummy database and repeats something that causes the backend to grow in 
memory usage? Trying to do this - by progressively cutting things out of 
your test until it stops growing - will help you track down what, 
exactly, is causing the growth.

It'd be helpful if you could also provide some general system 
information, as shown here:

    http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

--
Craig Ringer