pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Evgeny Gridasov <eugrid@fpm.kubsu.ru>
Cc: pgsql-performance@postgresql.org
Subject: Re: Background writer configuration
Date: Thu, 16 Mar 2006 15:58:53 -0600
Message-ID: <44198B3D.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <20060316211523.73343cee.eugrid@fpm.kubsu.ru>
References: <44181A11.EE98.0025.0@wicourts.gov>
	<20060316211523.73343cee.eugrid@fpm.kubsu.ru>

>>> On Thu, Mar 16, 2006 at 12:15 pm, in message
<20060316211523.73343cee.eugrid@fpm.kubsu.ru>, Evgeny Gridasov
<eugrid@fpm.kubsu.ru> wrote: 
> 
> please, could you post other settings from your postgresql.conf?

Everything in postgresql.conf which is not commented out:

listen_addresses = '*'          # what IP interface(s) to listen on;
max_connections = 600                   # note: increasing
max_connections costs
shared_buffers = 20000                  # min 16 or max_connections*2,
8KB each
work_mem = 10240                        # min 64, size in KB
max_fsm_pages = 1400000                 # min max_fsm_relations*16, 6
bytes each
bgwriter_lru_percent = 20.0             # 0-100% of LRU buffers
scanned/round
bgwriter_lru_maxpages = 200             # 0-1000 buffers max
written/round
bgwriter_all_percent = 10.0             # 0-100% of all buffers
scanned/round
bgwriter_all_maxpages = 600             # 0-1000 buffers max
written/round
full_page_writes = off                  # recover from partial page
writes
wal_buffers = 20                        # min 4, 8KB each
checkpoint_segments = 10                # in logfile segments, min 1,
16MB each
effective_cache_size = 524288           # typically 8KB each
random_page_cost = 2                    # units are one sequential page
fetch
redirect_stderr = on                    # Enable capturing of stderr
into log
log_line_prefix = '[%m] %p %q<%u %d %r> '                       #
Special values:
stats_start_collector = on
stats_block_level = on
stats_row_level = on
autovacuum = true                       # enable autovacuum
subprocess?
autovacuum_naptime = 10         # time between autovacuum runs, in
secs
autovacuum_vacuum_threshold = 1 # min # of tuple updates before
autovacuum_analyze_threshold = 1        # min # of tuple updates
before
autovacuum_vacuum_scale_factor = 0.2    # fraction of rel size before
autovacuum_analyze_scale_factor = 0.1   # fraction of rel size before
lc_messages = 'C'                       # locale for system error
message
lc_monetary = 'C'                       # locale for monetary
formatting
lc_numeric = 'C'                        # locale for number formatting
lc_time = 'C'                           # locale for time formatting
sql_inheritance = off
standard_conforming_strings = on




view thread (14+ messages)  latest in thread

Message-ID: <44198B3D.EE98.0025.0@wicourts.gov>
Permalink:  ../44198B3D.EE98.0025.0@wicourts.gov/
Also on:    postgresql.org/message-id/44198B3D.EE98.0025.0@wicourts.gov

 · 

reply

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, eugrid@fpm.kubsu.ru
  Subject: Re: Background writer configuration
  In-Reply-To: <44198B3D.EE98.0025.0@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