Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id AD8089F935F for ; Tue, 28 Aug 2007 19:50:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 70340-03 for ; Tue, 28 Aug 2007 19:50:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 0221A9F9F75 for ; Tue, 28 Aug 2007 19:50:05 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l7SMnuEs011207; Tue, 28 Aug 2007 18:49:56 -0400 (EDT) To: Simon Riggs cc: Robert Treat , pgsql-admin@postgresql.org Subject: Re: how is pitr replay interruption time determined? In-reply-to: <1188341069.4218.93.camel@ebony.site> References: <200708271742.57392.xzilla@users.sourceforge.net> <10268.1188256622@sss.pgh.pa.us> <200708281739.34094.xzilla@users.sourceforge.net> <4555.1188338360@sss.pgh.pa.us> <1188341069.4218.93.camel@ebony.site> Comments: In-reply-to Simon Riggs message dated "Tue, 28 Aug 2007 23:44:29 +0100" Date: Tue, 28 Aug 2007 18:49:56 -0400 Message-ID: <11206.1188341396@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/371 X-Sequence-Number: 26702 Simon Riggs writes: > Yeh, we traced a problem with GIN indexes to this cause in early June; > Teodor fixed it quickly in REL8_2_STABLE, but that won't be available > until 8.2.5. Thanks, that's what I missed finding ... Robert, do you have any GIN indexes in this DB? > I'd be happier with a log message to say > ereport(DEBUG2, > (errmsg("RM %d not safe to record restart point at %X/%X", > rmid, > checkPoint->redo.xlogid, > checkPoint->redo.xrecoff))); > to help trace such things in future. As long as it's DEBUG2 or so, no objection here. regards, tom lane