Re: [PATCHES] updated hash functions for postgresql v1

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Asko Oja <ascoja(at)gmail(dot)com>
Cc: 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-02-11 16:22:13
Message-ID: 10333.1234369333@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Asko Oja <ascoja(at)gmail(dot)com> writes:
> Did this change hashtext() visible to users? We have been using it quite
> widely for partitioning our databases. If so then it should be marked quite
> visibly in release notes as there might be others who will be hit by this.

The hash functions are undocumented, have changed in the past, and are
likely to change again in the future. If you are using them in a way
that depends on them to give the same answers across versions, you'd
better stop.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-02-11 16:24:44 Re: A deprecation policy
Previous Message David Fetter 2009-02-11 16:19:38 Re: Optimization rules for semi and anti joins