From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: pitr standby on slave with skewed time
Date: Fri, 11 Jul 2008 18:15:57 +0100
Message-ID: <1215796557.4051.1551.camel@ebony.2ndQuadrant> (raw)
In-Reply-To: <6522.1215792939@sss.pgh.pa.us>
References: <200807111119.46117.xzilla@users.sourceforge.net>
<6522.1215792939@sss.pgh.pa.us>
On Fri, 2008-07-11 at 12:15 -0400, Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > Was review a clients config/setup and ran across a pitr warm standby scenario
> > where the master machine is set to the current time, but the slave's time is
> > currently sitting back in the month of May. Outside of getting ntp setup on
> > the machine, I am wondering if I need to do anything special with the
> > postgresql setup, or if just setting the correct date on the machine is a
> > safe enough operation that nothing else would need to be done (like re-doing
> > the base backup). Any thoughts?
>
> AFAIR you should be all right ... PITR only looks at WAL indexes, not
> file timestamps.
WAL filenames, just in case anybody listening thinks "I didn't create an
index on my WAL, should I?". This is so people that set their pg_xlog
filesystem no file modification timestamps don't screw up their
recovery.
> The slave does watch the current time to decide when to do recovery
> restartpoints, so if you were setting the clock *back* by a large amount
> it might be wise to stop and restart the slave postmaster. Forward
> should be no problem though.
Yeh, you're good.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
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: simon@2ndquadrant.com, tgl@sss.pgh.pa.us, xzilla@users.sourceforge.net
Subject: Re: pitr standby on slave with skewed time
In-Reply-To: <1215796557.4051.1551.camel@ebony.2ndQuadrant>
* 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