Re: [PATCHES] updated hash functions for postgresql v1

From: Hannu Krosing <hannu(at)2ndQuadrant(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Asko Oja <ascoja(at)gmail(dot)com>, Kenneth Marshall <ktm(at)rice(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCHES] updated hash functions for postgresql v1
Date: 2009-10-29 08:54:24
Message-ID: 1256806464.13214.92.camel@hvost1700
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2009-10-29 at 09:47 +0200, Peter Eisentraut wrote:
> On Wed, 2009-10-28 at 12:51 -0700, Jeff Davis wrote:
> > Trying to develop and document a set of standardized, stable hash
> > functions covering a wide range of possible use cases sounds like it may
> > be better served by an extension.
>
> I suspect that some of the participants in this thread have PL/Proxy in
> mind.

Yes, I think that pl/proxy is the prime example of such use.

> PL/Proxy should probably ship its own set of hash functions.

Or maybe we could just extract the hashes form some version of stock
postgresql (say 8.3) and then make those available in contrib under the
name "stable_hashes" ?

> If we ever get built-in partitioning by hash (see thread nearby and most
> previous ones like it), we should also think about providing a hash
> function that doesn't change output over versions and is independent of
> hash index implementation concerns.

And maybe even documented ;)

--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2009-10-29 08:54:53 Re: Proposal - temporal contrib module
Previous Message Pavel Stehule 2009-10-29 08:48:46 Grouping sets