Skip site navigation (1) Skip section navigation (2)

Re: Warm standby problems: Followup

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "David F(dot) Skoll" <dfs(at)roaringpenguin(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Warm standby problems: Followup
Date: 2009-10-27 19:42:17
Message-ID: 4AE706C9020000250002C037@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-admin
"David F. Skoll" <dfs(at)roaringpenguin(dot)com> wrote:
 
> shared_buffers = 24MB
 
You should probably set that higher.  Different workloads favor
different settings, but if you've got any reasonable amount of RAM for
a modern machine, somewhere between 256MB and one-third of total RAM
is usually best.
 
> archive_command = '/usr/bin/wal_archive_command.pl %p'
 
It would probably be safer to pass in %f, too, and use it for the file
name rather than plucking off the last portion of the %p -- at a
minimum it might reduce the chances that you'd use that technique in
restore_command, where it flat out won't work.
 
> autovacuum = off
 
Be very careful if you choose to do this -- you've just made yourself
responsible for preventing bloat which can slowly strangle
performance.
 
There are a few setting which should almost always be overridden for
production use.  You might want to read this for a start:
 
http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
 
None of those, however, seem likely to cause the problem you describe.
Back to blaming the OS.
 
On the other hand, it's possible that tuning these up might change the
timings such that you don't hit the OS bug so often.
 
-Kevin

In response to

Responses

pgsql-admin by date

Next:From: David F. SkollDate: 2009-10-27 19:56:16
Subject: Re: Warm standby problems: Followup
Previous:From: David F. SkollDate: 2009-10-27 19:31:07
Subject: Re: Warm standby problems: Followup

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group