Re: [PATCHES] updated hash functions for postgresql v1 - Mailing list pgsql-hackers

From Hannu Krosing
Subject Re: [PATCHES] updated hash functions for postgresql v1
Date
Msg-id 1256765183.13214.43.camel@hvost1700
Whole thread Raw
In response to Re: [PATCHES] updated hash functions for postgresql v1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, 2009-10-28 at 15:31 -0400, Tom Lane wrote:
> Hannu Krosing <hannu@2ndQuadrant.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




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Parsing config files in a directory
Next
From: Simon Riggs
Date:
Subject: Re: Parsing config files in a directory