From: Rod Taylor <pg@rbt.ca>
To: alemon@tiago.hazor.com.br
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: slow database
Date: Wed, 11 Feb 2004 09:49:26 -0500
Message-ID: <1076510965.761.17.camel@jester> (raw)
In-Reply-To: <1076509411.402a3ae38d9b8@tiago.hazor.com.br>
References: <1076509411.402a3ae38d9b8@tiago.hazor.com.br>
On Wed, 2004-02-11 at 09:23, alemon@tiago.hazor.com.br wrote:
> my data base is very slow. The machine is a processor Xeon 2GB with
> 256 MB of RAM DDR. My archive of configuration is this:
I'm not surprised. New values below old.
> sort_mem = 131072 # min 64, size in KB
sort_mem = 8192.
> fsync = false
Are you aware of the potential for data corruption during a hardware,
power or software failure?
> enable_seqscan = false
> enable_indexscan = false
> enable_tidscan = false
> enable_sort = false
> enable_nestloop = false
> enable_mergejoin = false
> enable_hashjoin = false
You want all of these set to true, not false.
> effective_cache_size = 170000 # typically 8KB each
effective_cache_size = 16384.
> random_page_cost = 1000000000 # units are one sequential page fetch cost
random_page_cost = 3
> cpu_tuple_cost = 0.3 # (same)
cpu_tuple_cost = 0.01
> cpu_index_tuple_cost = 0.6 # (same)
cpu_index_tuple_cost = 0.001
> cpu_operator_cost = 0.7 # (same)
cpu_operator_cost = 0.0025
> default_statistics_target = 1 # range 1-1000
default_statistics_target = 10
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: pg@rbt.ca, alemon@tiago.hazor.com.br
Subject: Re: slow database
In-Reply-To: <1076510965.761.17.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