From: Gaetano Mendola <mendola@bigfoot.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Determining current WAL
Date: Wed, 23 Feb 2005 02:25:16 +0100
Message-ID: <421BDB7C.1040401@bigfoot.com> (raw)
In-Reply-To: <7183.1108654412@sss.pgh.pa.us>
References: <OF103D09D2.83838038-ON80256FAB.0037B300-80256FAB.00398245@transport.alstom.com>
<7183.1108654412@sss.pgh.pa.us>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mendola@bigfoot.com, tgl@sss.pgh.pa.us
Subject: Re: Determining current WAL
In-Reply-To: <421BDB7C.1040401@bigfoot.com>
References: <OF103D09D2.83838038-ON80256FAB.0037B300-80256FAB.00398245@transport.alstom.com> <7183.1108654412@sss.pgh.pa.us> <421BDB7C.1040401@bigfoot.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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