| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Selena Deckelmann <selenamarie(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Dividing progress/debug information in pg_standby, and stat before copy |
| Date: | 2010-01-26 00:08:54 |
| Message-ID: | 1264464534.24669.2201.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-01-26 00:09:57 | Re: Dividing progress/debug information in pg_standby, and stat before copy |
| Previous Message | Tom Lane | 2010-01-26 00:01:41 | Re: Possible changes to pg_restore |