From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Chris <ctlajoie(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: How to troubleshoot high mem usage by postgres? |
Date: | 2010-02-27 22:38:53 |
Message-ID: | 4B899EFD.90200@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-02-27 22:39:33 | Re: How to troubleshoot high mem usage by postgres? |
Previous Message | Chris | 2010-02-27 22:29:13 | How to troubleshoot high mem usage by postgres? |