On Mon, Sep 21, 2009 at 10:47 AM, Alan McKay <alan(dot)mckay(at)gmail(dot)com> wrote:
> We are looking to optimize the query I was talking about last week
> which is killing our system.
> We have explain and analyze which tell us about the cost of a query
> time-wise, but what does one use to determine (and trace / predict?)
> memory consumption?
I'm not sure what to suggest, other than the available operating
system tools, but if you post EXPLAIN ANALYZE output we might be able
to speculate better.
Setting work_mem too high is a frequent cause of problems of this sort, I think.
In response to
pgsql-performance by date
|Next:||From: Bruce Momjian||Date: 2009-09-21 21:19:29|
|Subject: Re: statement stats extra load?|
|Previous:||From: astro77||Date: 2009-09-21 19:51:56|
|Subject: Re: Slow select times on select with xpath|