On Tue, 2010-10-26 at 14:08 -0400, Tom Lane wrote:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> >> * Operations on hash indexes are not presently WAL-logged, so replay will not update these indexes. Hash indexes will not be used for query plans during recovery.
> > The initial patch indeed had a special-case in the planner to ignore
> > hash indexes during hot standby, but it was left out because the lack of
> > WAL-logging is a general problem with hash indexes, not a hot standby
> > issue.
> Yeah, and also the index would still be broken after the slave exits hot
> standby and becomes live; so that hack didn't cure the problem anyway.
OK, that's a good argument.
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
In response to
pgsql-bugs by date
|Next:||From: Dobes Vandermeer||Date: 2010-10-26 21:45:35|
|Subject: BUG #5728: Unexpected behavior comparing result of age() to an interval|
|Previous:||From: Heikki Linnakangas||Date: 2010-10-26 18:48:44|
|Subject: Re: Recovery bug|