From: Steve Atkins <steve@blighty.com>
To: pgsql-performance@postgresql.org
Subject: Re: Planner constants for RAM resident databases
Date: Fri, 1 Jul 2005 19:08:23 -0700
Message-ID: <20050702020823.GA32264@gp.word-to-the-wise.com> (raw)
In-Reply-To: <200507012159.39041.emil@baymountain.com>
References: <200507012159.39041.emil@baymountain.com>
On Fri, Jul 01, 2005 at 09:59:38PM -0400, Emil Briggs wrote:
> I'm working with an application where the database is entirely resident in RAM
> (the server is a quad opteron with 16GBytes of memory). It's a web
> application and handles a high volume of queries. The planner seems to be
> generating poor plans for some of our queries which I can fix by raising
> cpu_tuple_cost. I have seen some other comments in the archives saying that
> this is a bad idea but is that necessarily the case when the database is
> entirely resident in RAM?
If I'm understanding correctly that'll mostly increase the estimated
cost of handling a row relative to a sequential page fetch, which
sure sounds like it'll push plans in the right direction, but it
doesn't sound like the right knob to twiddle.
What do you have random_page_cost set to?
Cheers,
Steve
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: steve@blighty.com
Subject: Re: Planner constants for RAM resident databases
In-Reply-To: <20050702020823.GA32264@gp.word-to-the-wise.com>
References: <200507012159.39041.emil@baymountain.com> <20050702020823.GA32264@gp.word-to-the-wise.com>
* 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