Re: Determining current WAL - Mailing list pgsql-admin

From Gaetano Mendola
Subject Re: Determining current WAL
Date
Msg-id 421BDB7C.1040401@bigfoot.com
Whole thread Raw
In response to Re: Determining current WAL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tom Lane wrote:
> thomas.revell@powerconv.alstom.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



pgsql-admin by date:

Previous
From: "Chris White (cjwhite)"
Date:
Subject: Re: 7.4.5 file write issue
Next
From: Vinicius
Date:
Subject: Problem with "/etc/alternatives/java" and "pg74.215.jdbc3.jar".