X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 63AD5D1B380 for ; Wed, 21 Jul 2004 21:43:12 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 32009-03 for ; Thu, 22 Jul 2004 00:43:10 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id F2D47D1B1D1 for ; Wed, 21 Jul 2004 21:43:06 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i6M0h72w023763; Wed, 21 Jul 2004 20:43:08 -0400 (EDT) To: Mark Kirkwood Cc: Simon Riggs , pgsql-hackers@postgresql.org Subject: Re: PITR COPY Failure (was Point in Time Recovery) In-reply-to: <40FF0CDF.4070509@coretech.co.nz> References: <200407141555.i6EFtnk22984@mail.osdl.org> <1089833620.17493.4624.camel@stromboli> <40F5E14A.4090003@coretech.co.nz> <1089875702.17493.5539.camel@stromboli> <40F652C6.4070007@coretech.co.nz> <1089935215.17493.6906.camel@stromboli> <40FA0F93.8010607@coretech.co.nz> <40FC6BF2.5050701@coretech.co.nz> <3607.1090296869@sss.pgh.pa.us> <1090324635.28049.2554.camel@stromboli> <7787.1090327914@sss.pgh.pa.us> <1090329086.28049.2708.camel@stromboli> <13342.1090332035@sss.pgh.pa.us> <1090333455.28049.2917.camel@stromboli> <22835.1090449835@sss.pgh.pa.us> <40FF0CDF.4070509@coretech.co.nz> Comments: In-reply-to Mark Kirkwood message dated "Thu, 22 Jul 2004 12:39:59 +1200" Date: Wed, 21 Jul 2004 20:43:07 -0400 Message-ID: <23762.1090456987@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/1195 X-Sequence-Number: 56756 Mark Kirkwood writes: > Looks good to me. Log file numbering scheme seems to have changed - is > that part of the fix too?. That's for timelines ... it's not directly related but I thought I should put in both changes at once to avoid forcing an extra initdb. regards, tom lane