From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | alemon(at)tiago(dot)hazor(dot)com(dot)br |
Cc: | Postgresql Performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: slow database |
Date: | 2004-02-11 14:49:26 |
Message-ID: | 1076510965.761.17.camel@jester |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, 2004-02-11 at 09:23, alemon(at)tiago(dot)hazor(dot)com(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Trawick | 2004-02-11 15:36:00 | Re: slow database |
Previous Message | PC Drew | 2004-02-11 14:44:42 | Re: slow database |