aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2009-04-04 04:53:43 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2009-04-04 04:53:43 +0000
commit9462a22ab61ff49a79eeac860b66bb0dd6405266 (patch)
treef99bf2687ef18bdefc56d1967c3a69ccc9049c83 /src/backend/access/gist/gistproc.c
parentdf3a497603c2a6ce296ed49d10a40243068ebb19 (diff)
downloadpostgresql-9462a22ab61ff49a79eeac860b66bb0dd6405266.tar.gz
postgresql-9462a22ab61ff49a79eeac860b66bb0dd6405266.zip
Rewrite interval_hash() so that the hashcodes are equal for values that
interval_eq() considers equal. I'm not sure how that fundamental requirement escaped us through multiple revisions of this hash function, but there it is; it's been wrong since interval_hash was first written for PG 7.1. Per bug #4748 from Roman Kononov. Backpatch to all supported releases. This patch changes the contents of hash indexes for interval columns. That's no particular problem for PG 8.4, since we've broken on-disk compatibility of hash indexes already; but it will require a migration warning note in the next minor releases of all existing branches: "if you have any hash indexes on columns of type interval, REINDEX them after updating".
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions