From: Robert Treat <xzilla@users.sourceforge.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: how is pitr replay interruption time determined?
Date: Tue, 28 Aug 2007 17:39:33 -0400
Message-ID: <200708281739.34094.xzilla@users.sourceforge.net> (raw)
In-Reply-To: <10268.1188256622@sss.pgh.pa.us>
References: <200708271742.57392.xzilla@users.sourceforge.net>
<10268.1188256622@sss.pgh.pa.us>
On Monday 27 August 2007 19:17, Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > LOG: database system was interrupted while in recovery at log time
> > 2007-07-30 19:17:37 EDT
> >
> > I am curious how this date is determined by postgres/pitr?
>
> It's the update timestamp in pg_control, which in essence is going to be
> the completion time of the last checkpoint. If the crash was during WAL
> recovery, as it seems to be, it'd be the time the last "restart"
> checkpoint was made.
>
Is there some way to force checkpoints on a db doing wal replay?
Also, I would think at a minimum that the last "restart" checkpoint would be
akin to when the db was last started, but looking at my replay instance I
see:
pg_control last modified: Mon Aug 27 12:12:55 2007
Time of latest checkpoint: Mon Jul 30 19:17:37 2007
The first date is around the time I restarted the instance, the second is
still a mystery to me. Perhaps I am misinterpreting your respone?
--
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, tgl@sss.pgh.pa.us
Subject: Re: how is pitr replay interruption time determined?
In-Reply-To: <200708281739.34094.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