pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: kadams@mxlogic.com
Cc: Jim C. Nasby <decibel@decibel.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL file utilization question
Date: Wed, 16 May 2007 16:02:57 -0400
Message-ID: <6775.1179345777@sss.pgh.pa.us> (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>

Keaton Adams <kadams@mxlogic.com> writes:
> Well, no, I'm not that paranoid where I expect checkpoints to be taking
> place so often.  I do find it interesting that controlling checkpoint
> frequency is a factor of the number of WAL files available.  In order to
> get up to 60 second checkpoints I had to set checkpoint_segments to 25,
> which resulted in the creation of 52 log files in data/pg_xlog.  So for
> 120 second checkpoints I will need to have up to 104 log files in
> data/pg_xlog available?

No, it's nonlinear, precisely because of the
checkpoints-increase-the-log-size effect.  Given the size of modern
disks, I don't see why a couple Gb of WAL space is a problem anyhow
for a large database.

			regards, tom lane



view thread (8+ messages)

Message-ID: <6775.1179345777@sss.pgh.pa.us>
Permalink:  ../6775.1179345777@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6775.1179345777@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, kadams@mxlogic.com, decibel@decibel.org
  Subject: Re: WAL file utilization question
  In-Reply-To: <6775.1179345777@sss.pgh.pa.us>

* 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