| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | 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 17:47:42 |
| Message-ID: | 28670.1288115262@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)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 after a 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-10-26 18:01:09 | Re: BUG #5727: Indexes broken in streaming replication |
| Previous Message | Heikki Linnakangas | 2010-10-26 17:38:13 | Re: BUG #5727: Indexes broken in streaming replication |