| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
| Cc: | Christopher Petrilli <petrilli(at)gmail(dot)com>, Ying Lu <ying_lu(at)cs(dot)concordia(dot)ca>, pgsql-general(at)postgresql(dot)org, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL |
| Date: | 2005-05-09 16:38:41 |
| Message-ID: | 427F9211.2090008@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
Jim C. Nasby wrote:
> Having indexes that people shouldn't be using does add confusion for
> users, and presents the opportunity for foot-shooting.
Emitting a warning/notice on hash-index creation is something I've
suggested in the past -- that would be fine with me.
> Even if there is some kind of advantage (would they possibly speed up
> hash joins?)
No, hash joins and hash indexes are unrelated.
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zlatko Matic | 2005-05-09 16:45:19 | backup compress...blobs/insert commands/verbose messages |
| Previous Message | Jim C. Nasby | 2005-05-09 16:34:23 | Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-05-09 16:51:33 | Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL |
| Previous Message | Jim C. Nasby | 2005-05-09 16:34:23 | Re: [PERFORM] "Hash index" vs. "b-tree index" (PostgreSQL |