Re: Dividing progress/debug information in pg_standby, and stat before copy - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Dividing progress/debug information in pg_standby, and stat before copy
Date
Msg-id 1264464534.24669.2201.camel@ebony
Whole thread Raw
In response to Re: Dividing progress/debug information in pg_standby, and stat before copy  (Greg Smith <greg@2ndquadrant.com>)
Responses Re: Dividing progress/debug information in pg_standby, and stat before copy
List pgsql-hackers
On Mon, 2010-01-25 at 16:34 -0500, Greg Smith wrote:
> Josh Berkus wrote:
> > We discussed this issue at LCA where I encountered these bogus error
> > messages when I was doing the demo of HS.  I consider Selena's patch to
> > be a bug-fix for beta of 9.0, not a feature.  Currently the database
> > reports a lot of false error messages when running in standby mode, and
> > once we have 1000's more users using standby mode, we're going to see a
> > lot of related confusion.
> >   
> 
> Does anyone have a complete list of the false error messages and what 
> context they show up in so that a proper test case could be constructed?

Just committed a fix: the server no longer requests 0000000001.history
at start of archive recovery.

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Possible changes to pg_restore
Next
From: Tom Lane
Date:
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy