From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Jewell <c(dot)jewell(at)lancaster(dot)ac(dot)uk>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: WAL log archive frequency |
Date: | 2006-01-19 20:53:23 |
Message-ID: | 200601192053.k0JKrNj16672@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom Lane wrote:
> Chris Jewell <c(dot)jewell(at)lancaster(dot)ac(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-01-19 21:00:06 | Re: Distributed database with postgres |
Previous Message | Tom Lane | 2006-01-19 20:42:47 | Re: killing a query safely |