Skip site navigation (1) Skip section navigation (2)

Re: Determining current WAL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: thomas(dot)revell(at)powerconv(dot)alstom(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Determining current WAL
Date: 2005-02-17 15:33:32
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
thomas(dot)revell(at)powerconv(dot)alstom(dot)com writes:
> I'm currently looking at using WAL / PITR backups for a database, and I 
> need to keep the backups as up to date as possible. As such, keeping a 
> copy of the current WAL file, as suggested in the manual, would seem to be 
> a very good idea. I'm slightly confused, though, about which file is the 
> current. I had assumed that it would always be the highest numbered,

No.  Go with the most-recently-modified.  Segment files are normally
created (or renamed into place) in advance of being needed.

There should probably be a cleaner/more reliable way of identifying
the active file ...

			regards, tom lane

In response to


pgsql-admin by date

Next:From: thomas.revellDate: 2005-02-17 15:36:16
Subject: Re: Determining current WAL
Previous:From: Gourish SingbalDate: 2005-02-17 11:54:10
Subject: ERROR: 40P01:

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group