Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 70F419FA1BE for ; Tue, 28 Aug 2007 20:31:27 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 67289-04 for ; Tue, 28 Aug 2007 20:31:24 -0300 (ADT) X-Greylist: delayed 00:19:47.918608 by SQLgrey-1.7.5 Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by postgresql.org (Postfix) with ESMTP id B05819F9E7B for ; Tue, 28 Aug 2007 20:31:24 -0300 (ADT) Received: from [192.168.0.5] (84-12-84-169.dyn.gotadsl.co.uk [84.12.84.169]) by smtp.nildram.co.uk (Postfix) with ESMTP id 0E2B92BA0B0; Wed, 29 Aug 2007 00:11:35 +0100 (BST) Subject: Re: how is pitr replay interruption time determined? From: Simon Riggs To: Tom Lane Cc: Robert Treat , pgsql-admin@postgresql.org In-Reply-To: <11206.1188341396@sss.pgh.pa.us> 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> <11206.1188341396@sss.pgh.pa.us> Content-Type: text/plain Date: Wed, 29 Aug 2007 00:13:07 +0100 Message-Id: <1188342787.4218.98.camel@ebony.site> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200708/374 X-Sequence-Number: 26705 On Tue, 2007-08-28 at 18:49 -0400, Tom Lane wrote: > 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. OK, I'll do up a patch. References: - GIN error trace patch on pgsql-general http://archives.postgresql.org/pgsql-general/2007-06/msg00072.php - Committed fixes http://archives.postgresql.org/pgsql-committers/2007-06/msg00061.php -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com