From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andy Shellam (Mailing Lists) <andy.shellam-lists@mailnetwork.co.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: [Fwd: Checkpoint Location Format]
Date: Tue, 07 Nov 2006 10:02:39 -0500
Message-ID: <9899.1162911759@sss.pgh.pa.us> (raw)
In-Reply-To: <45509711.8080807@mailnetwork.co.uk>
References: <45509711.8080807@mailnetwork.co.uk>
"Andy Shellam (Mailing Lists)" <andy.shellam-lists@mailnetwork.co.uk> writes:
> Further to the below e-mail, I've come across a slight problem.
> The starting checkpoint location in a backup I've just taken is
> "0/22A3190" (note: 7 digits after the /, not 6 as I first thought.)
> However the .backup file is called <WAL_FILE>.002A3190 (ie. it only
> takes the right-most 6 digits).
Yeah, the second part of the .backup file name is the offset within the
corresponding WAL file, which for the standard file size of 16M can only
range up to 6 hex digits. The higher-order bits of the second word of
the checkpoint location go into the last part of the WAL file name.
That is, checkpoint location xxxxxxxx/yyzzzzzz should be associated
with a backup file named like ttttttttxxxxxxxx000000yy.00zzzzzz.backup.
(I think ... haven't had any caffeine yet this morning ...)
regards, tom lane
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: tgl@sss.pgh.pa.us, andy.shellam-lists@mailnetwork.co.uk
Subject: Re: [Fwd: Checkpoint Location Format]
In-Reply-To: <9899.1162911759@sss.pgh.pa.us>
References: <45509711.8080807@mailnetwork.co.uk> <9899.1162911759@sss.pgh.pa.us>
* 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