mirror of
https://github.com/postgres/postgres.git
synced 2025-04-20 00:42:27 +03:00
This reverts commit 9f984ba6d23dc6eecebf479ab1d3f2e550a4e9be. 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.
38 lines
1.1 KiB
SQL
38 lines
1.1 KiB
SQL
-- macaddr check
|
|
|
|
CREATE TABLE macaddrtmp (a macaddr);
|
|
|
|
\copy macaddrtmp from 'data/macaddr.data'
|
|
|
|
SET enable_seqscan=on;
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a < '22:00:5c:e5:9b:0d';
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a <= '22:00:5c:e5:9b:0d';
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a = '22:00:5c:e5:9b:0d';
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a >= '22:00:5c:e5:9b:0d';
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a > '22:00:5c:e5:9b:0d';
|
|
|
|
CREATE INDEX macaddridx ON macaddrtmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a < '22:00:5c:e5:9b:0d'::macaddr;
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a <= '22:00:5c:e5:9b:0d'::macaddr;
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a = '22:00:5c:e5:9b:0d'::macaddr;
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a >= '22:00:5c:e5:9b:0d'::macaddr;
|
|
|
|
SELECT count(*) FROM macaddrtmp WHERE a > '22:00:5c:e5:9b:0d'::macaddr;
|
|
|
|
-- Test index-only scans
|
|
SET enable_bitmapscan=off;
|
|
EXPLAIN (COSTS OFF)
|
|
SELECT * FROM macaddrtmp WHERE a < '02:03:04:05:06:07'::macaddr;
|
|
SELECT * FROM macaddrtmp WHERE a < '02:03:04:05:06:07'::macaddr;
|