pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim C. Nasby <decibel@decibel.org>
To: Keaton Adams <kadams@mxlogic.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL file utilization question
Date: Wed, 16 May 2007 11:51:43 -0500
Message-ID: <20070516165143.GU14548@nasby.net> (raw)
In-Reply-To: <1179334144.22514.14.camel@MXLRMT-208.corp.mxlogic.com>
References: <1179332909.22514.3.camel@MXLRMT-208.corp.mxlogic.com>
	<20070516163513.GQ14548@nasby.net>
	<1179334144.22514.14.camel@MXLRMT-208.corp.mxlogic.com>

On Wed, May 16, 2007 at 10:49:04AM -0600, Keaton Adams wrote:
> So, if I do set the checkpoint_segments parameter to 50, 75, or even 100
> I will have a considerable number of WAL files in data/pg_xlog, but they
> will be used more efficiently, so I will be archiving less?  That's what
> I understand from the comments received so far.

Yes. Let it create 500 or 1000 WAL files if it wants... it's much more
important to limit the frequency of checkpoints than to reduce the
number of WAL files (which has virtually no impact on performance).
-- 
Jim Nasby                                      decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



view thread (8+ messages)  latest in thread

Message-ID: <20070516165143.GU14548@nasby.net>
Permalink:  ../20070516165143.GU14548@nasby.net/
Also on:    postgresql.org/message-id/20070516165143.GU14548@nasby.net

 · 

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-admin@postgresql.org
  Cc: decibel@decibel.org, kadams@mxlogic.com
  Subject: Re: WAL file utilization question
  In-Reply-To: <20070516165143.GU14548@nasby.net>

* 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