From: | Paul A Jungwirth <pj(at)illuminatedcomputing(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | range test for hash index? |
Date: | 2019-09-13 19:17:59 |
Message-ID: | CA+renyV=Us-5XfMC25bNp-uWSj39XgHHmGE9Rh2cQKMegSj52g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
I noticed the tests for range types do this:
create table numrange_test2(nr numrange);
create index numrange_test2_hash_idx on numrange_test2 (nr);
Does that need a `using hash`? It seems like that's the intention. We
only use that table for equality comparisions. The script already
creates a table with a btree index further up. If I don't drop the
table I can see it's not a hash index:
regression=# \d numrange_test2
Table "public.numrange_test2"
Column | Type | Collation | Nullable | Default
--------+----------+-----------+----------+---------
nr | numrange | | |
Indexes:
"numrange_test2_hash_idx" btree (nr)
Everything else passes if I change just that one line in the
{sql,expected} files.
Regards,
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2019-09-13 19:22:50 | Re: Write visibility map during CLUSTER/VACUUM FULL |
Previous Message | James Coleman | 2019-09-13 18:29:28 | Re: [DOC] Document auto vacuum interruption |