| From: | Kenneth Marshall <ktm(at)rice(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com>, Asko Oja <ascoja(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] updated hash functions for postgresql v1 |
| Date: | 2009-10-28 19:35:36 |
| Message-ID: | 20091028193536.GB9312@it.is.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 28, 2009 at 03:31:17PM -0400, Tom Lane wrote:
> Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
> > I had never checked the docs for hash functions, but I had assumed, that
> > internal functions are prefixed by pg_ and anything else is public, free
> > to use functionality.
>
> Sure, it's free to use. It's not free to assume that we promise never
> to change it.
>
> > Changing hash functions also makes in-place upgrades a lot harder, as
> > they can't be done incrementally anymore for tables which use hash
> > indexes.
>
> Hash indexes are so far from being production-grade that this argument
> is not significant.
>
> regards, tom lane
In addition that change from 8.3 -> 8.4 to store only the hash and not
the value in the index means that a reindex would be required in any event.
Cheers,
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-10-28 19:51:49 | Re: [PATCHES] updated hash functions for postgresql v1 |
| Previous Message | Tom Lane | 2009-10-28 19:31:17 | Re: [PATCHES] updated hash functions for postgresql v1 |