From: Dan Langille <dan@langille.org>
To: Rod Taylor <ports@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: seq scan woes
Date: Mon, 07 Jun 2004 16:12:40 -0400
Message-ID: <40C493F8.1181.48F37175@localhost> (raw)
In-Reply-To: <1086638426.86807.40.camel@jester>
References: <40C48DA6.3356.48DAC2EB@localhost>
On 7 Jun 2004 at 16:00, Rod Taylor wrote:
> 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?
Nothing recently (ie. past few months). Nothing at all really.
Perhaps I need to start tuning that.
> Could you send explain analyse again with SEQ_SCAN enabled but with
> nested loops disabled?
See http://rafb.net/paste/results/zpJEvb28.html
13s
> 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.
I grep'd postgresql.conf:
#effective_cache_size = 1000 # typically 8KB each
#random_page_cost = 4 # units are one sequential page fetch cost
NOTE: both above are commented out.
Thank you
--
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/
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: dan@langille.org, ports@rbt.ca
Subject: Re: seq scan woes
In-Reply-To: <40C493F8.1181.48F37175@localhost>
* 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