| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Small Release Notes Comment |
| Date: | 2007-09-17 11:09:30 |
| Message-ID: | 87tzpto8et.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I think the change to the hash functions needs to be called out in the release
notes.
If anyone stored any results of hashintN, hashfloat8, etc in their database or
outside the database those results will have changed. It's fairly unlikely but
there could be someone out there doing that.
No intervention is required for normal expression indexes using those
functions or hash indexes which will be rebuilt during a database upgrade
anyways. I don't think hash_any itself changed so this wouldn't affect
hashtext or any hash function which was already using hash_any.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-09-17 11:18:39 | Re: [COMMITTERS] pgsql: Fix up text concatenation so that it accepts all the reasonable |
| Previous Message | Tom Lane | 2007-09-17 04:02:47 | Re: invalidly encoded strings |