postgresql/contrib/btree_gist/expected/cidr.out
Heikki Linnakangas d92b1cdbab Revert "Add sortsupport for gist_btree opclasses, for faster index builds."
This reverts commit 9f984ba6d2.

It was making the buildfarm unhappy, apparently setting client_min_messages
in a regression test produces different output if log_statement='all'.
Another issue is that I now suspect the bit sortsupport function was in
fact not correct to call byteacmp(). Revert to investigate both of those
issues.
2021-04-07 14:33:21 +03:00

67 lines
1.1 KiB
Plaintext

-- cidr check
CREATE TABLE cidrtmp AS
SELECT cidr(a) AS a FROM inettmp ;
SET enable_seqscan=on;
SELECT count(*) FROM cidrtmp WHERE a < '121.111.63.82';
count
-------
290
(1 row)
SELECT count(*) FROM cidrtmp WHERE a <= '121.111.63.82';
count
-------
291
(1 row)
SELECT count(*) FROM cidrtmp WHERE a = '121.111.63.82';
count
-------
1
(1 row)
SELECT count(*) FROM cidrtmp WHERE a >= '121.111.63.82';
count
-------
310
(1 row)
SELECT count(*) FROM cidrtmp WHERE a > '121.111.63.82';
count
-------
309
(1 row)
CREATE INDEX cidridx ON cidrtmp USING gist ( a );
SET enable_seqscan=off;
SELECT count(*) FROM cidrtmp WHERE a < '121.111.63.82'::cidr;
count
-------
290
(1 row)
SELECT count(*) FROM cidrtmp WHERE a <= '121.111.63.82'::cidr;
count
-------
291
(1 row)
SELECT count(*) FROM cidrtmp WHERE a = '121.111.63.82'::cidr;
count
-------
1
(1 row)
SELECT count(*) FROM cidrtmp WHERE a >= '121.111.63.82'::cidr;
count
-------
310
(1 row)
SELECT count(*) FROM cidrtmp WHERE a > '121.111.63.82'::cidr;
count
-------
309
(1 row)