| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Asko Oja <ascoja(at)gmail(dot)com>, Kenneth Marshall <ktm(at)rice(dot)edu>, 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 21:26:23 |
| Message-ID: | 1256765183.13214.43.camel@hvost1700 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2009-10-28 at 15:31 -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.
AFAIK in-place upgrade is also not quite production-grade, so this was
meant as a forward-looking note for next time the hashxxx functions will
change.
> regards, tom lane
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2009-10-28 22:35:45 | Re: Show schema size with \dn+ |
| Previous Message | Andrew Dunstan | 2009-10-28 21:08:00 | Re: Parsing config files in a directory |