From: Chris Jewell <c.jewell@lancaster.ac.uk>
To: pgsql-admin@postgresql.org
Subject: WAL log archive frequency
Date: Thu, 19 Jan 2006 10:44:35 +0000
Message-ID: <43CF6D93.2080806@lancaster.ac.uk> (raw)
Hi,
Further to my question on PITR, I have now implemented it :-) However,
I was wondering about the frequency of archiving the WAL. Does
postgresql wait until the current WAL file has reached 16MB before
calling the archive_command? The reason why I ask is that last night,
after doing the base backup, I noticed that a WAL file had been written
to my backup server. This morning, I added a primary key to a table but
noticed that nothing was written to the backup server. Should it have
been?
Is there any method of forcing a WAL segment to be archived at a given
frequency irrespective of whether or not it is a full 16MB? Our
database changes so infrequently at the moment that I'm worried that
these small changes may not be backed up regularly by the PITR system.
Thanks,
Chris
--
Chris Jewell, BSc(Hons), BVSc, MRCVS
Dept of Maths and Statistics
Fylde College
Lancaster University
Lancaster
Lancs
LA1 4YF
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: c.jewell@lancaster.ac.uk
Subject: Re: WAL log archive frequency
In-Reply-To: <43CF6D93.2080806@lancaster.ac.uk>
References: <43CF6D93.2080806@lancaster.ac.uk>
* 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