From: Steinar H. Gunderson <sgunderson@bigfoot.com>
To: Abu Mushayeed <abumushayeed@yahoo.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: CPU Intensive query
Date: Fri, 18 May 2007 18:42:10 +0200
Message-ID: <20070518164210.GA15372@uio.no> (raw)
In-Reply-To: <877956.83201.qm@web57112.mail.re3.yahoo.com>
References: <877956.83201.qm@web57112.mail.re3.yahoo.com>
On Fri, May 18, 2007 at 09:02:52AM -0700, Abu Mushayeed wrote:
> I have an interesting problem. I have the following query that ran ok on
> Monday and Tuesday and it has been running ok since I have been at this
> job. I have seen it to be IO intensive, but since Wednesday it has become
> CPU intensive. Database wise fresh data has been put into the tables,
> vacuumed & analyzed, no other parameter has been modified.
What Postgres version is this?
> The query is as follows and it's explain plan is also attached:
Normally EXPLAIN ANALYZE data would be much better than EXPLAIN, but if the
query indeed does not finish, it's not going to help much.
> set enable_nestloop = off;
What's the rationale for this?
> HashAggregate (cost=152555.97..152567.32 rows=267 width=162)
152000 disk page fetches is a bit, but it shouldn't take 24 hours. There's
probably misestimation involved at some point here. Does it really return 267
rows, or many more?
/* Steinar */
--
Homepage: http://www.sesse.net/
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: sgunderson@bigfoot.com, abumushayeed@yahoo.com
Subject: Re: CPU Intensive query
In-Reply-To: <20070518164210.GA15372@uio.no>
* 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