2000-01-05 07:07:58 +01:00
|
|
|
--
|
|
|
|
-- INET
|
1998-10-27 20:34:18 +01:00
|
|
|
--
|
|
|
|
|
|
|
|
-- prepare the table...
|
|
|
|
|
|
|
|
DROP TABLE INET_TBL;
|
|
|
|
CREATE TABLE INET_TBL (c cidr, i inet);
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1', '192.168.1.226/24');
|
2004-10-08 03:45:37 +02:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.0/26', '192.168.1.226');
|
2001-06-17 04:05:20 +02:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1', '192.168.1.0/24');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1', '192.168.1.0/25');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1', '192.168.1.255/24');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1', '192.168.1.255/25');
|
1998-10-27 20:34:18 +01:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10', '10.1.2.3/8');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10.0.0.0', '10.1.2.3/8');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10.1.2.3', '10.1.2.3/32');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10.1.2', '10.1.2.3/24');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10.1', '10.1.2.3/16');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10', '10.1.2.3/8');
|
1998-10-29 19:13:03 +01:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10', '11.1.2.3/8');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10', '9.1.2.3/8');
|
2003-06-25 00:21:24 +02:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10:23::f1', '10:23::f1/64');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10:23::8000/113', '10:23::ffff');
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('::ffff:1.2.3.4', '::4.3.2.1/24');
|
2000-10-27 03:55:23 +02:00
|
|
|
-- check that CIDR rejects invalid input:
|
2004-10-08 03:45:37 +02:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226');
|
2003-06-25 00:21:24 +02:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4');
|
2001-06-13 23:09:00 +02:00
|
|
|
-- check that CIDR rejects invalid input when converting from text:
|
2004-10-08 03:45:37 +02:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES (cidr('192.168.1.2/30'), '192.168.1.226');
|
2003-06-25 00:21:24 +02:00
|
|
|
INSERT INTO INET_TBL (c, i) VALUES (cidr('ffff:ffff:ffff:ffff::/24'), '::192.168.1.226');
|
1998-10-29 19:13:03 +01:00
|
|
|
SELECT '' AS ten, c AS cidr, i AS inet FROM INET_TBL;
|
1998-10-27 20:34:18 +01:00
|
|
|
|
|
|
|
-- now test some support functions
|
|
|
|
|
2003-06-25 00:21:24 +02:00
|
|
|
SELECT '' AS ten, i AS inet, host(i), text(i), family(i) FROM INET_TBL;
|
1998-10-29 19:13:03 +01:00
|
|
|
SELECT '' AS ten, c AS cidr, broadcast(c),
|
|
|
|
i AS inet, broadcast(i) FROM INET_TBL;
|
|
|
|
SELECT '' AS ten, c AS cidr, network(c) AS "network(cidr)",
|
|
|
|
i AS inet, network(i) AS "network(inet)" FROM INET_TBL;
|
|
|
|
SELECT '' AS ten, c AS cidr, masklen(c) AS "masklen(cidr)",
|
|
|
|
i AS inet, masklen(i) AS "masklen(inet)" FROM INET_TBL;
|
1998-10-27 20:34:18 +01:00
|
|
|
|
1998-10-29 19:13:03 +01:00
|
|
|
SELECT '' AS four, c AS cidr, masklen(c) AS "masklen(cidr)",
|
|
|
|
i AS inet, masklen(i) AS "masklen(inet)" FROM INET_TBL
|
1998-10-27 20:34:18 +01:00
|
|
|
WHERE masklen(c) <= 8;
|
|
|
|
|
1998-10-29 19:13:03 +01:00
|
|
|
SELECT '' AS six, c AS cidr, i AS inet FROM INET_TBL
|
1998-10-27 20:34:18 +01:00
|
|
|
WHERE c = i;
|
|
|
|
|
1998-10-29 19:13:03 +01:00
|
|
|
SELECT '' AS ten, i, c,
|
2010-11-23 21:27:50 +01:00
|
|
|
i < c AS lt, i <= c AS le, i = c AS eq,
|
1998-10-29 19:13:03 +01:00
|
|
|
i >= c AS ge, i > c AS gt, i <> c AS ne,
|
|
|
|
i << c AS sb, i <<= c AS sbe,
|
Add an in-core GiST index opclass for inet/cidr types.
This operator class can accelerate subnet/supernet tests as well as
btree-equivalent ordered comparisons. It also handles a new network
operator inet && inet (overlaps, a/k/a "is supernet or subnet of"),
which is expected to be useful in exclusion constraints.
Ideally this opclass would be the default for GiST with inet/cidr data,
but we can't mark it that way until we figure out how to do a more or
less graceful transition from the current situation, in which the
really-completely-bogus inet/cidr opclasses in contrib/btree_gist are
marked as default. Having the opclass in core and not default is better
than not having it at all, though.
While at it, add new documentation sections to allow us to officially
document GiST/GIN/SP-GiST opclasses, something there was never a clear
place to do before. I filled these in with some simple tables listing
the existing opclasses and the operators they support, but there's
certainly scope to put more information there.
Emre Hasegeli, reviewed by Andreas Karlsson, further hacking by me
2014-04-08 21:46:14 +02:00
|
|
|
i >> c AS sup, i >>= c AS spe,
|
|
|
|
i && c AS ovr
|
1998-10-29 19:13:03 +01:00
|
|
|
FROM INET_TBL;
|
|
|
|
|
2014-08-29 04:37:58 +02:00
|
|
|
SELECT max(i) AS max, min(i) AS min FROM INET_TBL;
|
|
|
|
SELECT max(c) AS max, min(c) AS min FROM INET_TBL;
|
|
|
|
|
2001-06-13 23:09:00 +02:00
|
|
|
-- check the conversion to/from text and set_netmask
|
2003-01-15 17:35:50 +01:00
|
|
|
SELECT '' AS ten, set_masklen(inet(text(i)), 24) FROM INET_TBL;
|
Add an in-core GiST index opclass for inet/cidr types.
This operator class can accelerate subnet/supernet tests as well as
btree-equivalent ordered comparisons. It also handles a new network
operator inet && inet (overlaps, a/k/a "is supernet or subnet of"),
which is expected to be useful in exclusion constraints.
Ideally this opclass would be the default for GiST with inet/cidr data,
but we can't mark it that way until we figure out how to do a more or
less graceful transition from the current situation, in which the
really-completely-bogus inet/cidr opclasses in contrib/btree_gist are
marked as default. Having the opclass in core and not default is better
than not having it at all, though.
While at it, add new documentation sections to allow us to officially
document GiST/GIN/SP-GiST opclasses, something there was never a clear
place to do before. I filled these in with some simple tables listing
the existing opclasses and the operators they support, but there's
certainly scope to put more information there.
Emre Hasegeli, reviewed by Andreas Karlsson, further hacking by me
2014-04-08 21:46:14 +02:00
|
|
|
|
|
|
|
-- check that btree index works correctly
|
2003-01-15 17:35:50 +01:00
|
|
|
CREATE INDEX inet_idx1 ON inet_tbl(i);
|
|
|
|
SET enable_seqscan TO off;
|
2003-01-15 21:01:01 +01:00
|
|
|
SELECT * FROM inet_tbl WHERE i<<'192.168.1.0/24'::cidr;
|
|
|
|
SELECT * FROM inet_tbl WHERE i<<='192.168.1.0/24'::cidr;
|
2003-01-15 17:35:50 +01:00
|
|
|
SET enable_seqscan TO on;
|
|
|
|
DROP INDEX inet_idx1;
|
2001-06-17 04:05:20 +02:00
|
|
|
|
Add an in-core GiST index opclass for inet/cidr types.
This operator class can accelerate subnet/supernet tests as well as
btree-equivalent ordered comparisons. It also handles a new network
operator inet && inet (overlaps, a/k/a "is supernet or subnet of"),
which is expected to be useful in exclusion constraints.
Ideally this opclass would be the default for GiST with inet/cidr data,
but we can't mark it that way until we figure out how to do a more or
less graceful transition from the current situation, in which the
really-completely-bogus inet/cidr opclasses in contrib/btree_gist are
marked as default. Having the opclass in core and not default is better
than not having it at all, though.
While at it, add new documentation sections to allow us to officially
document GiST/GIN/SP-GiST opclasses, something there was never a clear
place to do before. I filled these in with some simple tables listing
the existing opclasses and the operators they support, but there's
certainly scope to put more information there.
Emre Hasegeli, reviewed by Andreas Karlsson, further hacking by me
2014-04-08 21:46:14 +02:00
|
|
|
-- check that gist index works correctly
|
|
|
|
CREATE INDEX inet_idx2 ON inet_tbl using gist (i inet_ops);
|
|
|
|
SET enable_seqscan TO off;
|
|
|
|
SELECT * FROM inet_tbl WHERE i << '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i <<= '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i && '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i >>= '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i >> '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i < '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i <= '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i = '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i >= '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i > '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT * FROM inet_tbl WHERE i <> '192.168.1.0/24'::cidr ORDER BY i;
|
2015-03-28 14:11:53 +01:00
|
|
|
|
|
|
|
-- test index-only scans
|
|
|
|
EXPLAIN (COSTS OFF)
|
|
|
|
SELECT i FROM inet_tbl WHERE i << '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
SELECT i FROM inet_tbl WHERE i << '192.168.1.0/24'::cidr ORDER BY i;
|
|
|
|
|
Add an in-core GiST index opclass for inet/cidr types.
This operator class can accelerate subnet/supernet tests as well as
btree-equivalent ordered comparisons. It also handles a new network
operator inet && inet (overlaps, a/k/a "is supernet or subnet of"),
which is expected to be useful in exclusion constraints.
Ideally this opclass would be the default for GiST with inet/cidr data,
but we can't mark it that way until we figure out how to do a more or
less graceful transition from the current situation, in which the
really-completely-bogus inet/cidr opclasses in contrib/btree_gist are
marked as default. Having the opclass in core and not default is better
than not having it at all, though.
While at it, add new documentation sections to allow us to officially
document GiST/GIN/SP-GiST opclasses, something there was never a clear
place to do before. I filled these in with some simple tables listing
the existing opclasses and the operators they support, but there's
certainly scope to put more information there.
Emre Hasegeli, reviewed by Andreas Karlsson, further hacking by me
2014-04-08 21:46:14 +02:00
|
|
|
SET enable_seqscan TO on;
|
|
|
|
DROP INDEX inet_idx2;
|
|
|
|
|
2006-02-11 21:39:59 +01:00
|
|
|
-- simple tests of inet boolean and arithmetic operators
|
|
|
|
SELECT i, ~i AS "~i" FROM inet_tbl;
|
|
|
|
SELECT i, c, i & c AS "and" FROM inet_tbl;
|
|
|
|
SELECT i, c, i | c AS "or" FROM inet_tbl;
|
|
|
|
SELECT i, i + 500 AS "i+500" FROM inet_tbl;
|
|
|
|
SELECT i, i - 500 AS "i-500" FROM inet_tbl;
|
|
|
|
SELECT i, c, i - c AS "minus" FROM inet_tbl;
|
|
|
|
SELECT '127.0.0.1'::inet + 257;
|
|
|
|
SELECT ('127.0.0.1'::inet + 257) - 257;
|
|
|
|
SELECT '127::1'::inet + 257;
|
|
|
|
SELECT ('127::1'::inet + 257) - 257;
|
|
|
|
SELECT '127.0.0.2'::inet - ('127.0.0.2'::inet + 500);
|
|
|
|
SELECT '127.0.0.2'::inet - ('127.0.0.2'::inet - 500);
|
|
|
|
SELECT '127::2'::inet - ('127::2'::inet + 500);
|
|
|
|
SELECT '127::2'::inet - ('127::2'::inet - 500);
|
|
|
|
-- these should give overflow errors:
|
|
|
|
SELECT '127.0.0.1'::inet + 10000000000;
|
|
|
|
SELECT '127.0.0.1'::inet - 10000000000;
|
|
|
|
SELECT '126::1'::inet - '127::2'::inet;
|
|
|
|
SELECT '127::1'::inet - '126::2'::inet;
|
|
|
|
-- but not these
|
|
|
|
SELECT '127::1'::inet + 10000000000;
|
|
|
|
SELECT '127::1'::inet - '127::2'::inet;
|
2015-05-05 20:22:24 +02:00
|
|
|
|
|
|
|
-- insert one more row with addressed from different families
|
|
|
|
INSERT INTO INET_TBL (c, i) VALUES ('10', '10::/8');
|
|
|
|
-- now, this one should fail
|
|
|
|
SELECT inet_merge(c, i) FROM INET_TBL;
|
|
|
|
-- fix it by inet_same_family() condition
|
|
|
|
SELECT inet_merge(c, i) FROM INET_TBL WHERE inet_same_family(c, i);
|