From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-performance@postgresql.org
To: Richard Kojedzinszky <krichy@tvnetwork.hu>
Subject: Re: query optimization
Date: Thu, 26 Apr 2012 13:23:38 -0500
Message-ID: <4F994C5A02000025000473FD@gw.wicourts.gov> (raw)
In-Reply-To: <alpine.DEB.2.02.1204241008570.9591@krichy.tvnetwork.hu>
References: <alpine.DEB.2.02.1204241008570.9591@krichy.tvnetwork.hu>
Richard Kojedzinszky <krichy@tvnetwork.hu> wrote:
> tuning our installation to not to use sequence scans in this case?
Make sure effective_cache_size is set to the sum of shared_buffers
and whatever your OS shows as usable for caching. Try adjusting
cost factors: maybe random_page_cost between 1 and 2, and
cpu_tuple_cost between 0.03 and 0.05.
-Kevin
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: Kevin.Grittner@wicourts.gov, krichy@tvnetwork.hu
Subject: Re: query optimization
In-Reply-To: <4F994C5A02000025000473FD@gw.wicourts.gov>
* 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