Re: Age of the WAL?

From: Erik Jones <ejones(at)engineyard(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Age of the WAL?
Date: 2013-03-26 22:12:00
Message-ID: A53C29A1-F981-49CE-BA73-24992FD31EB7@engineyard.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Mar 12, 2013, at 4:13 PM, Tom Lane wrote:

> Erik Jones <ejones(at)engineyard(dot)com> writes:
>> What's the best way to determine the age of the current WAL? Not the current segment, but the whole thing. Put another way: is there a way to determine a timestamp for the oldest available transaction in the WAL?
>
> Transaction commit and abort records carry timestamps, so you could
> figure this out with something like pg_xlogdump. I don't know of any
> canned solution though.

Tom,

Thanks, and sorry for any discontinuity in the rather long time it's taken for me to get on this reply (had a vacation).

Anyway, will pg_xlogdump work with any previous versions of Postgres or will it be only 9.3+?

For reference, the reason need to be able to do this is this: Given a set of snapshots (each taken with running pg_start_backup before and pg_stop_backup after) and a running server, I need to be able to determine whether or not any given snapshot will be usable for setting up a new standby. I know I could grab the info returned from pg_start_backup and store that as snapshot meta-data but I'm hoping to keep from having to make changes the existing snapshotting code, if possible.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2013-03-26 22:21:10 Re: Age of the WAL?
Previous Message Laurence Rowe 2013-03-26 21:59:19 Building an invalidation queue in Postgres