Re: Checkpoint Location Format - Mailing list pgsql-admin

From Andy Shellam (Mailing Lists)
Subject Re: Checkpoint Location Format
Date
Msg-id 4552FAB5.6010008@mailnetwork.co.uk
Whole thread Raw
In response to Re: Checkpoint Location Format  ("Jim C. Nasby" <jim@nasby.net>)
List pgsql-admin
Hi Jim,

Tom did answer actually!  (Although it was first thing in the morning
and he hadn't had any caffeine so he may have forgot to copy the list in
;) )
I forget what he said the format was now, and I haven't got his e-mail,
but I've just done a regex to match one or more characters before and
after the "/", which works.

Andy.

Jim C. Nasby wrote:
> On Tue, Nov 07, 2006 at 01:12:53PM +0000, Andy Shellam (Mailing Lists) wrote:
>
>> Hi,
>>
>> I'm writing an automated file-system level backup application for use
>> with WAL archiving, that will issue the pg_start_backup call, tar and
>> gzip the cluster data directory, issue the pg_stop_backup call, and
>> remove all previous un-needed WAL files from the archive.
>>
>> I need to write a regular expression that will search for the WAL
>> filename and checkpoint location from the backup_label file, and just
>> want to clarify that the checkpoint location will always be of the
>> format: X/XXXXXX - where X is one of 0-9, A-F?
>>
>> And then the WAL .backup file that is generated in the archive, has a
>> filename of the form:
>>
>> <WAL_FILE>.00XXXXXX.backup
>>
>> where <WAL_FILE> is the name of the "STARTING WAL LOCATION" directive in
>> the backup_label file, and XXXXXX is the last 6 digits of the checkpoint
>> (after the / )?
>>
>
> I don't know the answer, but since no one's replied I suggest looking in
> the code. Looking at the source of pg_start_backup would probably be a
> good start, though I'm guessing the real answer is somewhere in the
> backend.
>


pgsql-admin by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: statistics buffer is full
Next
From: "Paolo Negri"
Date:
Subject: Re: pg_dump and foreign keys troubles