Re: size of units in postgresql.conf

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Vincent Stoessel <vincent(at)xaymaca(dot)com>, Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: size of units in postgresql.conf
Date: 2002-08-27 02:38:24
Message-ID: 200208270238.g7R2cOR29406@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Here is the 7.3 postgresql.conf file, where I have added units to the
> > file.
>
> Aren't these misleading if one is using nonstandard BLCKSZ?

Yep, I remembered it but forgot later. I added "typically" to the 8k
mention in all places.

>
> > #shared_buffers = 64 # 2*max_connections, min 16, 8K each
> > #wal_buffers = 8 # min 4, 8K each
> > #effective_cache_size = 1000 # 8K each
>
>
> These could usefully be labeled as "unit is cost of a sequential page
> fetch":
>
> > #random_page_cost = 4
> > #cpu_tuple_cost = 0.01
> > #cpu_index_tuple_cost = 0.001
> > #cpu_operator_cost = 0.0025

Nice, it is now:

#random_page_cost = 4 # units are one sequential page fetch cost
#cpu_tuple_cost = 0.01 # (same)
#cpu_index_tuple_cost = 0.001 # (same)
#cpu_operator_cost = 0.0025 # (same)

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2002-08-27 02:39:10 Re: size of units in postgresql.conf
Previous Message Alvaro Herrera 2002-08-27 00:40:44 Re: size of units in postgresql.conf