Re: [Fwd: Checkpoint Location Format]

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Andy Shellam (Mailing Lists)" <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)uk>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [Fwd: Checkpoint Location Format]
Date: 2006-11-07 15:02:39
Message-ID: 9899.1162911759@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Andy Shellam (Mailing Lists)" <andy(dot)shellam-lists(at)mailnetwork(dot)co(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Jerry Sievers 2006-11-07 16:05:38 Manual sys catalog constraint setup to avoid downtime?
Previous Message Andy Shellam (Mailing Lists) 2006-11-07 14:24:17 [Fwd: Checkpoint Location Format]