postgresql/contrib/btree_gist/expected/inet.out
Heikki Linnakangas 9f984ba6d2 Add sortsupport for gist_btree opclasses, for faster index builds.
Commit 16fa9b2b30 introduced a faster way to build GiST indexes, by
sorting all the data. This commit adds the sortsupport functions needed
to make use of that feature for btree_gist.

Author: Andrey Borodin
Discussion: https://www.postgresql.org/message-id/2F3F7265-0D22-44DB-AD71-8554C743D943@yandex-team.ru
2021-04-07 13:22:05 +03:00

109 lines
2.4 KiB
Plaintext

-- inet check
CREATE TABLE inettmp (a inet);
\copy inettmp from 'data/inet.data'
SET enable_seqscan=on;
SELECT count(*) FROM inettmp WHERE a < '89.225.196.191';
count
-------
213
(1 row)
SELECT count(*) FROM inettmp WHERE a <= '89.225.196.191';
count
-------
214
(1 row)
SELECT count(*) FROM inettmp WHERE a = '89.225.196.191';
count
-------
1
(1 row)
SELECT count(*) FROM inettmp WHERE a >= '89.225.196.191';
count
-------
387
(1 row)
SELECT count(*) FROM inettmp WHERE a > '89.225.196.191';
count
-------
386
(1 row)
SET client_min_messages = DEBUG1;
CREATE INDEX inetidx ON inettmp USING gist ( a );
DEBUG: building index "inetidx" on table "inettmp" serially
DEBUG: using sorted GiST build
CREATE INDEX inetidx_b ON inettmp USING gist ( a ) WITH (buffering=on);
DEBUG: building index "inetidx_b" on table "inettmp" serially
DROP INDEX inetidx_b;
RESET client_min_messages;
SET enable_seqscan=off;
SELECT count(*) FROM inettmp WHERE a < '89.225.196.191'::inet;
count
-------
213
(1 row)
SELECT count(*) FROM inettmp WHERE a <= '89.225.196.191'::inet;
count
-------
214
(1 row)
SELECT count(*) FROM inettmp WHERE a = '89.225.196.191'::inet;
count
-------
1
(1 row)
SELECT count(*) FROM inettmp WHERE a >= '89.225.196.191'::inet;
count
-------
387
(1 row)
SELECT count(*) FROM inettmp WHERE a > '89.225.196.191'::inet;
count
-------
386
(1 row)
VACUUM ANALYZE inettmp;
-- gist_inet_ops lacks a fetch function, so this should not be index-only scan
EXPLAIN (COSTS OFF)
SELECT count(*) FROM inettmp WHERE a = '89.225.196.191'::inet;
QUERY PLAN
--------------------------------------------------
Aggregate
-> Index Scan using inetidx on inettmp
Index Cond: (a = '89.225.196.191'::inet)
(3 rows)
SELECT count(*) FROM inettmp WHERE a = '89.225.196.191'::inet;
count
-------
1
(1 row)
DROP INDEX inetidx;
CREATE INDEX ON inettmp USING gist (a gist_inet_ops, a inet_ops);
-- likewise here (checks for core planner bug)
EXPLAIN (COSTS OFF)
SELECT count(*) FROM inettmp WHERE a = '89.225.196.191'::inet;
QUERY PLAN
----------------------------------------------------
Aggregate
-> Index Scan using inettmp_a_a1_idx on inettmp
Index Cond: (a = '89.225.196.191'::inet)
(3 rows)
SELECT count(*) FROM inettmp WHERE a = '89.225.196.191'::inet;
count
-------
1
(1 row)