From: Craig Ringer <craig@postnewspapers.com.au>
To: Chris <ctlajoie@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to troubleshoot high mem usage by postgres?
Date: Sun, 28 Feb 2010 06:38:53 +0800
Message-ID: <4B899EFD.90200@postnewspapers.com.au> (raw)
In-Reply-To: <57033cf81002271429wb0da13am37b3cb6258103ea5@mail.gmail.com>
References: <57033cf81002271429wb0da13am37b3cb6258103ea5@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: craig@postnewspapers.com.au, ctlajoie@gmail.com
Subject: Re: How to troubleshoot high mem usage by postgres?
In-Reply-To: <4B899EFD.90200@postnewspapers.com.au>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox