pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Frederiko Costa <frederiko@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: archived WALL files question
Date: Mon, 19 Apr 2010 11:41:17 -0500
Message-ID: <4BCC415D0200002500030A6B@gw.wicourts.gov> (raw)
In-Reply-To: <4BCC7804.9070604@gmail.com>
References: <7965A9DCF12CC14984420BCC37B1608F25AC0B99AD@Elzar.grant.co.uk>
	<4BC6F21D0200002500030956@gw.wicourts.gov>
	<7965A9DCF12CC14984420BCC37B1608F25AC0B99E4@Elzar.grant.co.uk>
	<4BCC7804.9070604@gmail.com>

Frederiko Costa <frederiko@gmail.com> wrote:
 
> I noticed the new logs files don't get copied to the directory
> specified on the archive_command. It's only copied when I do the
> pg_start_backup()/pg_stop_backup() base backup. Is this behaviour
> only achieved if I set archive_timeout? I did not want to do that,
> because I thought as soon as the 16MB WAL segment file got created
> it would be copied to the exported directory.
 
Have you actually been filling up any 16MB WAL file segments?  How
have you determined that?  What happens when you run (as a database
superuser) this command?:
 
SELECT pg_switch_xlog();
 
If the reason you don't want to set archive_timeout is that you
don't want 16MB files piling up when there is little or no activity,
you might want to consider using pglesslog or pg_clearxlogtail. 
These can eliminate nearly all the cost of the more frequent logs.
 
-Kevin



view thread (15+ messages)  latest in thread

Message-ID: <4BCC415D0200002500030A6B@gw.wicourts.gov>
Permalink:  ../4BCC415D0200002500030A6B@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4BCC415D0200002500030A6B@gw.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, frederiko@gmail.com
  Subject: Re: archived WALL files question
  In-Reply-To: <4BCC415D0200002500030A6B@gw.wicourts.gov>
  References: <7965A9DCF12CC14984420BCC37B1608F25AC0B99AD@Elzar.grant.co.uk> <4BC6F21D0200002500030956@gw.wicourts.gov> <7965A9DCF12CC14984420BCC37B1608F25AC0B99E4@Elzar.grant.co.uk> <4BCC7804.9070604@gmail.com> <4BCC415D0200002500030A6B@gw.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