pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedWAL log archive frequency
3+ messages / 3 participants
[nested] [flat]
* WAL log archive frequency
@ 2006-01-19 10:44 Chris Jewell <c.jewell@lancaster.ac.uk>
2006-01-19 17:01 ` Re: WAL log archive frequency Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: Chris Jewell @ 2006-01-19 10:44 UTC (permalink / raw)
To: pgsql-admin
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: WAL log archive frequency
2006-01-19 10:44 WAL log archive frequency Chris Jewell <c.jewell@lancaster.ac.uk>
@ 2006-01-19 17:01 ` Tom Lane <tgl@sss.pgh.pa.us>
2006-01-19 20:53 ` Re: WAL log archive frequency Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 3+ messages in thread
From: Tom Lane @ 2006-01-19 17:01 UTC (permalink / raw)
To: Chris Jewell <c.jewell@lancaster.ac.uk>; +Cc: pgsql-admin
Chris Jewell <c.jewell@lancaster.ac.uk> writes:
> 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?
Yes. The assumption is the archive_command may be too stupid to deal
with archiving the same file more than once, and/or might have
performance issues with doing that, eg, if it's writing to tape or some
kind of write-once media.
You can do something like saving the newest-by-timestamp file in the
xlog directory every minute or whatever via a cron job. This ought to
be better integrated though ...
regards, tom lane
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: WAL log archive frequency
2006-01-19 10:44 WAL log archive frequency Chris Jewell <c.jewell@lancaster.ac.uk>
2006-01-19 17:01 ` Re: WAL log archive frequency Tom Lane <tgl@sss.pgh.pa.us>
@ 2006-01-19 20:53 ` Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 0 replies; 3+ messages in thread
From: Bruce Momjian @ 2006-01-19 20:53 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Chris Jewell <c.jewell@lancaster.ac.uk>; pgsql-admin
Tom Lane wrote:
> Chris Jewell <c.jewell@lancaster.ac.uk> writes:
> > 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?
>
> Yes. The assumption is the archive_command may be too stupid to deal
> with archiving the same file more than once, and/or might have
> performance issues with doing that, eg, if it's writing to tape or some
> kind of write-once media.
>
> You can do something like saving the newest-by-timestamp file in the
> xlog directory every minute or whatever via a cron job. This ought to
> be better integrated though ...
FYI, this is documented.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2006-01-19 20:53 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-01-19 10:44 WAL log archive frequency Chris Jewell <c.jewell@lancaster.ac.uk>
2006-01-19 17:01 ` Tom Lane <tgl@sss.pgh.pa.us>
2006-01-19 20:53 ` Bruce Momjian <pgman@candle.pha.pa.us>
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