Re: [PATCHES] updated hash functions for postgresql v1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
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 19:31:17
Message-ID: 3380.1256758277@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kenneth Marshall 2009-10-28 19:35:36 Re: [PATCHES] updated hash functions for postgresql v1
Previous Message Tom Lane 2009-10-28 19:28:09 Re: Parsing config files in a directory