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.
31 lines
786 B
SQL
31 lines
786 B
SQL
-- 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';
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a <= '121.111.63.82';
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a = '121.111.63.82';
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a >= '121.111.63.82';
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a > '121.111.63.82';
|
|
|
|
CREATE INDEX cidridx ON cidrtmp USING gist ( a );
|
|
|
|
SET enable_seqscan=off;
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a < '121.111.63.82'::cidr;
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a <= '121.111.63.82'::cidr;
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a = '121.111.63.82'::cidr;
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a >= '121.111.63.82'::cidr;
|
|
|
|
SELECT count(*) FROM cidrtmp WHERE a > '121.111.63.82'::cidr;
|