Re: BUG #5727: Indexes broken in streaming replication
| От | Tom Lane |
|---|---|
| Тема | Re: BUG #5727: Indexes broken in streaming replication |
| Дата | |
| Msg-id | 28670.1288115262@sss.pgh.pa.us обсуждение |
| Ответ на | Re: BUG #5727: Indexes broken in streaming replication (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>) |
| Ответы |
Re: BUG #5727: Indexes broken in streaming replication
|
| Список | pgsql-bugs |
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> There's a note in the docs about this:
>> Note: Hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with REINDEX
aftera database crash. For this reason, hash index use is presently discouraged.
> though it doesn't explicitly mention replication. Perhaps it should be
> updated to something like:
Yeah, I too just noticed that that caveat hadn't been updated.
> Note: Hash index operations are not presently WAL-logged, so hash
> indexes might need to be rebuilt with REINDEX after a database crash.
> They are also not replicated over streaming or file-based replication.
> For this reason, hash index use is presently discouraged.
s/this reason/these reasons/. Also maybe we should change this to a
<caution> or <warning> instead of just a <note>? Otherwise +1.
regards, tom lane
В списке pgsql-bugs по дате отправления: