Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E17636507C4 for ; Fri, 11 Jul 2008 12:43:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 01974-01-5 for ; Fri, 11 Jul 2008 12:43:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by postgresql.org (Postfix) with ESMTP id 592C16505F6 for ; Fri, 11 Jul 2008 12:27:41 -0300 (ADT) Received: from ridley.home ([71.179.5.175]) by vms173005.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K3U000Y2L8ZPWHJ@vms173005.mailsrvcs.net> for pgsql-admin@postgresql.org; Fri, 11 Jul 2008 10:19:47 -0500 (CDT) Date: Fri, 11 Jul 2008 11:19:45 -0400 From: Robert Treat Subject: pitr standby on slave with skewed time To: pgsql-admin@postgresql.org Message-id: <200807111119.46117.xzilla@users.sourceforge.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline User-Agent: KMail/1.9.9 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/114 X-Sequence-Number: 29724 Howdy folks, 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? -- Robert Treat Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL