| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Jan Kantert <jan-postgres(at)kantert(dot)net>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #5727: Indexes broken in streaming replication |
| Date: | 2010-10-26 21:16:02 |
| Message-ID: | 1288127762.1587.470.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dobes Vandermeer | 2010-10-26 21:45:35 | BUG #5728: Unexpected behavior comparing result of age() to an interval |
| Previous Message | Heikki Linnakangas | 2010-10-26 18:48:44 | Re: Recovery bug |