From: Rod Taylor <ports@rbt.ca>
To: Dan Langille <dan@langille.org>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: seq scan woes
Date: Mon, 07 Jun 2004 16:00:28 -0400
Message-ID: <1086638426.86807.40.camel@jester> (raw)
In-Reply-To: <40C48DA6.3356.48DAC2EB@localhost>
References: <40C48DA6.3356.48DAC2EB@localhost>
On Mon, 2004-06-07 at 15:45, Dan Langille wrote:
> A production system has had a query recently degrade in performance.
> What once took < 1s now takes over 1s. I have tracked down the
> problem to a working example.
What changes have you made to postgresql.conf?
Could you send explain analyse again with SEQ_SCAN enabled but with
nested loops disabled?
Off the cuff? I might hazard a guess that effective_cache is too low or
random_page_cost is a touch too high. Probably the former.
--
Rod Taylor <rbt [at] rbt [dot] ca>
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
PGP Key: http://www.rbt.ca/signature.asc
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: ports@rbt.ca, dan@langille.org
Subject: Re: seq scan woes
In-Reply-To: <1086638426.86807.40.camel@jester>
* 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