From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: how is pitr replay interruption time determined?
Date: Tue, 28 Aug 2007 18:49:56 -0400
Message-ID: <11206.1188341396@sss.pgh.pa.us> (raw)
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>
Simon Riggs <simon@2ndquadrant.com> 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
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: tgl@sss.pgh.pa.us, simon@2ndquadrant.com, xzilla@users.sourceforge.net
Subject: Re: how is pitr replay interruption time determined?
In-Reply-To: <11206.1188341396@sss.pgh.pa.us>
* 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