From: Emil Briggs <emil@baymountain.com>
To: pgsql-performance@postgresql.org
Subject: Planner constants for RAM resident databases
Date: Fri, 1 Jul 2005 21:59:38 -0400
Message-ID: <200507012159.39041.emil@baymountain.com> (raw)
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?
Emil
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: emil@baymountain.com
Subject: Re: Planner constants for RAM resident databases
In-Reply-To: <200507012159.39041.emil@baymountain.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