From: Robert Treat <xzilla@users.sourceforge.net>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: how is pitr replay interruption time determined?
Date: Wed, 29 Aug 2007 10:48:54 -0400
Message-ID: <200708291048.54662.xzilla@users.sourceforge.net> (raw)
In-Reply-To: <1188341069.4218.93.camel@ebony.site>
References: <200708271742.57392.xzilla@users.sourceforge.net>
<4555.1188338360@sss.pgh.pa.us>
<1188341069.4218.93.camel@ebony.site>
On Tuesday 28 August 2007 18:44, Simon Riggs wrote:
> On Tue, 2007-08-28 at 17:59 -0400, Tom Lane wrote:
> > Robert Treat <xzilla@users.sourceforge.net> writes:
> > > Is there some way to force checkpoints on a db doing wal replay?
> >
> > No, it's hardwired to do it when it sees a checkpoint record in the WAL
> > stream.
> >
> > > pg_control last modified: Mon Aug 27 12:12:55 2007
> > > Time of latest checkpoint: Mon Jul 30 19:17:37 2007
> >
> > After looking again at the code, the "last modified" time is the time
> > that a recovery checkpoint was last done, and the "latest checkpoint"
> > is the timestamp of the WAL-stream checkpoint record that triggered it.
> > In a situation where you're catching up on historical WAL they could be
> > far apart, but when a slave is just following the master there shouldn't
> > be a huge difference --- not more than the maximum time to fill a WAL
> > record and ship it over to the slave, for sure.
> >
> > (BTW, I misread it before --- it looks like the "at log time" value
> > printed at startup *is* taken from the checkpoint record that it's
> > trying to roll forward from.)
>
> That's correct. Sorry for not replying earlier; just back from hols.
>
> Jumping back to original thought: Robert, you should be using the last
> checkpoint location, not the last time to decide which xlogs to remove.
>
Looking at last checkpoint location in pg_control, I see:
Latest checkpoint location: 1C/8001E848
How does one translate that into an xlog file name?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: xzilla@users.sourceforge.net, simon@2ndquadrant.com, tgl@sss.pgh.pa.us
Subject: Re: how is pitr replay interruption time determined?
In-Reply-To: <200708291048.54662.xzilla@users.sourceforge.net>
* 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