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

Re: Determining current WAL

From: Gaetano Mendola <mendola(at)bigfoot(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Determining current WAL
Date: 2005-02-23 01:25:16
Message-ID: 421BDB7C.1040401@bigfoot.com (view raw or flat)
Thread:
Lists: pgsql-admin
Tom Lane wrote:
> 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 ...

Yes it was discussed during the attempt to create the log delivery to
another server in "replay" state, if the master was not responding then
it was usefull have a way to identify the active wal segment, at the time
I was identifing the current wall the last created one


Regards
Gaetano Mendola



In response to

pgsql-admin by date

Next:From: ViniciusDate: 2005-02-23 03:32:44
Subject: Problem with "/etc/alternatives/java" and "pg74.215.jdbc3.jar".
Previous:From: Chris White (cjwhite)Date: 2005-02-23 00:59:10
Subject: Re: 7.4.5 file write issue

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