rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/src/test/regress/expected/inet.out

377 lines
15 KiB
Plaintext
Raw Normal View History

Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
--
-- INET
--
-- prepare the table...
DROP TABLE INET_TBL;
Some small polishing of Mark Hollomon's cleanup of DROP command: might as well allow DROP multiple INDEX, RULE, TYPE as well. Add missing CommandCounterIncrement to DROP loop, which could cause trouble otherwise with multiple DROP of items affecting same catalog entries. Try to bring a little consistency to various error messages using 'does not exist', 'nonexistent', etc --- I standardized on 'does not exist' since that's what the vast majority of the existing uses seem to be.
2000-10-23 01:32:48 +02:00
ERROR: table "inet_tbl" does not exist
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
CREATE TABLE INET_TBL (c cidr, i inet);
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1', '192.168.1.226/24');
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.0/26', '192.168.1.226');
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
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');
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +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');
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');
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
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');
Disallow bits beyond the mask length for CIDR values, per discussion on pghackers. Arrange for the sort ordering of general INET values to be network part as major sort key, host part as minor sort key. I did not force an initdb for this change, but anyone who's running indexes on general INET values may need to recreate those indexes.
2000-10-27 03:55:23 +02:00
-- check that CIDR rejects invalid input:
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
INSERT INTO INET_TBL (c, i) VALUES ('192.168.1.2/30', '192.168.1.226');
ERROR: invalid cidr value: "192.168.1.2/30"
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
DETAIL: Value has bits set to right of mask.
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
INSERT INTO INET_TBL (c, i) VALUES ('1234::1234::1234', '::1.2.3.4');
Message editing: remove gratuitous variations in message wording, standardize terms, add some clarifications, fix some untranslatable attempts at dynamic message building.
2003-09-25 08:58:07 +02:00
ERROR: invalid input syntax for type cidr: "1234::1234::1234"
Attached is a patch adding following functions: inet(text), cidr(text): convert a text value into inet/cidr set_masklen(inet): set masklen on the inet value Patch also contains regression checks for these functions. Alex Pilosov
2001-06-13 23:09:00 +02:00
-- check that CIDR rejects invalid input when converting from text:
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
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');
ERROR: invalid cidr value: "192.168.1.2/30"
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
DETAIL: Value has bits set to right of mask.
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
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');
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
ERROR: invalid cidr value: "ffff:ffff:ffff:ffff::/24"
DETAIL: Value has bits set to right of mask.
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
SELECT '' AS ten, c AS cidr, i AS inet FROM INET_TBL;
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
ten | cidr | inet
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
-----+--------------------+------------------
| 192.168.1.0/24 | 192.168.1.226/24
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
| 192.168.1.0/26 | 192.168.1.226
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
| 192.168.1.0/24 | 192.168.1.0/24
| 192.168.1.0/24 | 192.168.1.0/25
| 192.168.1.0/24 | 192.168.1.255/24
| 192.168.1.0/24 | 192.168.1.255/25
| 10.0.0.0/8 | 10.1.2.3/8
| 10.0.0.0/32 | 10.1.2.3/8
| 10.1.2.3/32 | 10.1.2.3
| 10.1.2.0/24 | 10.1.2.3/24
| 10.1.0.0/16 | 10.1.2.3/16
| 10.0.0.0/8 | 10.1.2.3/8
| 10.0.0.0/8 | 11.1.2.3/8
| 10.0.0.0/8 | 9.1.2.3/8
| 10:23::f1/128 | 10:23::f1/64
| 10:23::8000/113 | 10:23::ffff
| ::ffff:1.2.3.4/128 | ::4.3.2.1/24
(17 rows)
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
-- now test some support functions
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
SELECT '' AS ten, i AS inet, host(i), text(i), family(i) FROM INET_TBL;
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
ten | inet | host | text | family
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
-----+------------------+---------------+------------------+--------
| 192.168.1.226/24 | 192.168.1.226 | 192.168.1.226/24 | 4
| 192.168.1.226 | 192.168.1.226 | 192.168.1.226/32 | 4
| 192.168.1.0/24 | 192.168.1.0 | 192.168.1.0/24 | 4
| 192.168.1.0/25 | 192.168.1.0 | 192.168.1.0/25 | 4
| 192.168.1.255/24 | 192.168.1.255 | 192.168.1.255/24 | 4
| 192.168.1.255/25 | 192.168.1.255 | 192.168.1.255/25 | 4
| 10.1.2.3/8 | 10.1.2.3 | 10.1.2.3/8 | 4
| 10.1.2.3/8 | 10.1.2.3 | 10.1.2.3/8 | 4
| 10.1.2.3 | 10.1.2.3 | 10.1.2.3/32 | 4
| 10.1.2.3/24 | 10.1.2.3 | 10.1.2.3/24 | 4
| 10.1.2.3/16 | 10.1.2.3 | 10.1.2.3/16 | 4
| 10.1.2.3/8 | 10.1.2.3 | 10.1.2.3/8 | 4
| 11.1.2.3/8 | 11.1.2.3 | 11.1.2.3/8 | 4
| 9.1.2.3/8 | 9.1.2.3 | 9.1.2.3/8 | 4
| 10:23::f1/64 | 10:23::f1 | 10:23::f1/64 | 6
| 10:23::ffff | 10:23::ffff | 10:23::ffff/128 | 6
| ::4.3.2.1/24 | ::4.3.2.1 | ::4.3.2.1/24 | 6
(17 rows)
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
SELECT '' AS ten, c AS cidr, broadcast(c),
Fix regression test now that code seems to work. Add tests for comparison operators.
1998-10-29 19:12:50 +01:00
i AS inet, broadcast(i) FROM INET_TBL;
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
ten | cidr | broadcast | inet | broadcast
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
-----+--------------------+------------------+------------------+---------------------------------------
| 192.168.1.0/24 | 192.168.1.255/24 | 192.168.1.226/24 | 192.168.1.255/24
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
| 192.168.1.0/26 | 192.168.1.63/26 | 192.168.1.226 | 192.168.1.226
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
| 192.168.1.0/24 | 192.168.1.255/24 | 192.168.1.0/24 | 192.168.1.255/24
| 192.168.1.0/24 | 192.168.1.255/24 | 192.168.1.0/25 | 192.168.1.127/25
| 192.168.1.0/24 | 192.168.1.255/24 | 192.168.1.255/24 | 192.168.1.255/24
| 192.168.1.0/24 | 192.168.1.255/24 | 192.168.1.255/25 | 192.168.1.255/25
| 10.0.0.0/8 | 10.255.255.255/8 | 10.1.2.3/8 | 10.255.255.255/8
| 10.0.0.0/32 | 10.0.0.0 | 10.1.2.3/8 | 10.255.255.255/8
| 10.1.2.3/32 | 10.1.2.3 | 10.1.2.3 | 10.1.2.3
| 10.1.2.0/24 | 10.1.2.255/24 | 10.1.2.3/24 | 10.1.2.255/24
| 10.1.0.0/16 | 10.1.255.255/16 | 10.1.2.3/16 | 10.1.255.255/16
| 10.0.0.0/8 | 10.255.255.255/8 | 10.1.2.3/8 | 10.255.255.255/8
| 10.0.0.0/8 | 10.255.255.255/8 | 11.1.2.3/8 | 11.255.255.255/8
| 10.0.0.0/8 | 10.255.255.255/8 | 9.1.2.3/8 | 9.255.255.255/8
| 10:23::f1/128 | 10:23::f1 | 10:23::f1/64 | 10:23::ffff:ffff:ffff:ffff/64
| 10:23::8000/113 | 10:23::ffff/113 | 10:23::ffff | 10:23::ffff
| ::ffff:1.2.3.4/128 | ::ffff:1.2.3.4 | ::4.3.2.1/24 | 0:ff:ffff:ffff:ffff:ffff:ffff:ffff/24
(17 rows)
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
SELECT '' AS ten, c AS cidr, network(c) AS "network(cidr)",
Fix regression test now that code seems to work. Add tests for comparison operators.
1998-10-29 19:12:50 +01:00
i AS inet, network(i) AS "network(inet)" FROM INET_TBL;
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
ten | cidr | network(cidr) | inet | network(inet)
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
-----+--------------------+--------------------+------------------+------------------
| 192.168.1.0/24 | 192.168.1.0/24 | 192.168.1.226/24 | 192.168.1.0/24
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
| 192.168.1.0/26 | 192.168.1.0/26 | 192.168.1.226 | 192.168.1.226/32
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
| 192.168.1.0/24 | 192.168.1.0/24 | 192.168.1.0/24 | 192.168.1.0/24
| 192.168.1.0/24 | 192.168.1.0/24 | 192.168.1.0/25 | 192.168.1.0/25
| 192.168.1.0/24 | 192.168.1.0/24 | 192.168.1.255/24 | 192.168.1.0/24
| 192.168.1.0/24 | 192.168.1.0/24 | 192.168.1.255/25 | 192.168.1.128/25
| 10.0.0.0/8 | 10.0.0.0/8 | 10.1.2.3/8 | 10.0.0.0/8
| 10.0.0.0/32 | 10.0.0.0/32 | 10.1.2.3/8 | 10.0.0.0/8
| 10.1.2.3/32 | 10.1.2.3/32 | 10.1.2.3 | 10.1.2.3/32
| 10.1.2.0/24 | 10.1.2.0/24 | 10.1.2.3/24 | 10.1.2.0/24
| 10.1.0.0/16 | 10.1.0.0/16 | 10.1.2.3/16 | 10.1.0.0/16
| 10.0.0.0/8 | 10.0.0.0/8 | 10.1.2.3/8 | 10.0.0.0/8
| 10.0.0.0/8 | 10.0.0.0/8 | 11.1.2.3/8 | 11.0.0.0/8
| 10.0.0.0/8 | 10.0.0.0/8 | 9.1.2.3/8 | 9.0.0.0/8
| 10:23::f1/128 | 10:23::f1/128 | 10:23::f1/64 | 10:23::/64
| 10:23::8000/113 | 10:23::8000/113 | 10:23::ffff | 10:23::ffff/128
| ::ffff:1.2.3.4/128 | ::ffff:1.2.3.4/128 | ::4.3.2.1/24 | ::/24
(17 rows)
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
SELECT '' AS ten, c AS cidr, masklen(c) AS "masklen(cidr)",
Fix regression test now that code seems to work. Add tests for comparison operators.
1998-10-29 19:12:50 +01:00
i AS inet, masklen(i) AS "masklen(inet)" FROM INET_TBL;
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
ten | cidr | masklen(cidr) | inet | masklen(inet)
-----+--------------------+---------------+------------------+---------------
| 192.168.1.0/24 | 24 | 192.168.1.226/24 | 24
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
| 192.168.1.0/26 | 26 | 192.168.1.226 | 32
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
| 192.168.1.0/24 | 24 | 192.168.1.0/24 | 24
| 192.168.1.0/24 | 24 | 192.168.1.0/25 | 25
| 192.168.1.0/24 | 24 | 192.168.1.255/24 | 24
| 192.168.1.0/24 | 24 | 192.168.1.255/25 | 25
| 10.0.0.0/8 | 8 | 10.1.2.3/8 | 8
| 10.0.0.0/32 | 32 | 10.1.2.3/8 | 8
| 10.1.2.3/32 | 32 | 10.1.2.3 | 32
| 10.1.2.0/24 | 24 | 10.1.2.3/24 | 24
| 10.1.0.0/16 | 16 | 10.1.2.3/16 | 16
| 10.0.0.0/8 | 8 | 10.1.2.3/8 | 8
| 10.0.0.0/8 | 8 | 11.1.2.3/8 | 8
| 10.0.0.0/8 | 8 | 9.1.2.3/8 | 8
| 10:23::f1/128 | 128 | 10:23::f1/64 | 64
| 10:23::8000/113 | 113 | 10:23::ffff | 128
| ::ffff:1.2.3.4/128 | 128 | ::4.3.2.1/24 | 24
(17 rows)
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
SELECT '' AS four, c AS cidr, masklen(c) AS "masklen(cidr)",
Fix regression test now that code seems to work. Add tests for comparison operators.
1998-10-29 19:12:50 +01:00
i AS inet, masklen(i) AS "masklen(inet)" FROM INET_TBL
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
WHERE masklen(c) <= 8;
Change default output formatting for CIDR to be unabbreviated, per recommendation from Paul Vixie. Add a new abbrev() function to produce abbreviated format as text. No forced initdb, but new function is not available unless you do an initdb or add the pg_proc row manually.
2000-12-22 19:00:24 +01:00
four | cidr | masklen(cidr) | inet | masklen(inet)
------+------------+---------------+------------+---------------
| 10.0.0.0/8 | 8 | 10.1.2.3/8 | 8
| 10.0.0.0/8 | 8 | 10.1.2.3/8 | 8
| 10.0.0.0/8 | 8 | 11.1.2.3/8 | 8
| 10.0.0.0/8 | 8 | 9.1.2.3/8 | 8
Fix regression test now that code seems to work. Add tests for comparison operators.
1998-10-29 19:12:50 +01:00
(4 rows)
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
SELECT '' AS six, c AS cidr, i AS inet FROM INET_TBL
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
WHERE c = i;
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
six | cidr | inet
-----+----------------+----------------
| 192.168.1.0/24 | 192.168.1.0/24
| 10.1.2.3/32 | 10.1.2.3
(2 rows)
Add new inet/cidr regression test. All regression tests pass on Linux/i686 with the current source tree.
1998-10-27 20:34:18 +01:00
Verified output from new psql. Include a few new tests for datetime/timespan arithmetic.
2000-01-05 07:06:23 +01:00
SELECT '' AS ten, i, c,
i < c AS lt, i <= c AS le, i = c AS eq,
Fix regression test now that code seems to work. Add tests for comparison operators.
1998-10-29 19:12:50 +01:00
i >= c AS ge, i > c AS gt, i <> c AS ne,
i << c AS sb, i <<= c AS sbe,
i >> c AS sup, i >>= c AS spe
FROM INET_TBL;
Error message editing in utils/adt. Again thanks to Joe Conway for doing the bulk of the heavy lifting ...
2003-07-27 06:53:12 +02:00
ten | i | c | lt | le | eq | ge | gt | ne | sb | sbe | sup | spe
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
-----+------------------+--------------------+----+----+----+----+----+----+----+-----+-----+-----
| 192.168.1.226/24 | 192.168.1.0/24 | f | f | f | t | t | t | f | t | f | t
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
| 192.168.1.226 | 192.168.1.0/26 | f | f | f | t | t | t | f | f | f | f
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
| 192.168.1.0/24 | 192.168.1.0/24 | f | t | t | t | f | f | f | t | f | t
| 192.168.1.0/25 | 192.168.1.0/24 | f | f | f | t | t | t | t | t | f | f
| 192.168.1.255/24 | 192.168.1.0/24 | f | f | f | t | t | t | f | t | f | t
| 192.168.1.255/25 | 192.168.1.0/24 | f | f | f | t | t | t | t | t | f | f
| 10.1.2.3/8 | 10.0.0.0/8 | f | f | f | t | t | t | f | t | f | t
| 10.1.2.3/8 | 10.0.0.0/32 | t | t | f | f | f | t | f | f | t | t
| 10.1.2.3 | 10.1.2.3/32 | f | t | t | t | f | f | f | t | f | t
| 10.1.2.3/24 | 10.1.2.0/24 | f | f | f | t | t | t | f | t | f | t
| 10.1.2.3/16 | 10.1.0.0/16 | f | f | f | t | t | t | f | t | f | t
| 10.1.2.3/8 | 10.0.0.0/8 | f | f | f | t | t | t | f | t | f | t
| 11.1.2.3/8 | 10.0.0.0/8 | f | f | f | t | t | t | f | f | f | f
| 9.1.2.3/8 | 10.0.0.0/8 | t | t | f | f | f | t | f | f | f | f
| 10:23::f1/64 | 10:23::f1/128 | t | t | f | f | f | t | f | f | t | t
| 10:23::ffff | 10:23::8000/113 | f | f | f | t | t | t | t | t | f | f
| ::4.3.2.1/24 | ::ffff:1.2.3.4/128 | t | t | f | f | f | t | f | f | t | t
(17 rows)
Fix regression test now that code seems to work. Add tests for comparison operators.
1998-10-29 19:12:50 +01:00
Attached is a patch adding following functions: inet(text), cidr(text): convert a text value into inet/cidr set_masklen(inet): set masklen on the inet value Patch also contains regression checks for these functions. Alex Pilosov
2001-06-13 23:09:00 +02:00
-- check the conversion to/from text and set_netmask
Add ORDER BY for inet regression, pointed out by Rod Taylor.
2003-01-15 17:35:50 +01:00
SELECT '' AS ten, set_masklen(inet(text(i)), 24) FROM INET_TBL;
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
ten | set_masklen
Attached is a patch adding following functions: inet(text), cidr(text): convert a text value into inet/cidr set_masklen(inet): set masklen on the inet value Patch also contains regression checks for these functions. Alex Pilosov
2001-06-13 23:09:00 +02:00
-----+------------------
| 192.168.1.226/24
| 192.168.1.226/24
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
| 192.168.1.0/24
| 192.168.1.0/24
| 192.168.1.255/24
| 192.168.1.255/24
Attached is a patch adding following functions: inet(text), cidr(text): convert a text value into inet/cidr set_masklen(inet): set masklen on the inet value Patch also contains regression checks for these functions. Alex Pilosov
2001-06-13 23:09:00 +02:00
| 10.1.2.3/24
| 10.1.2.3/24
| 10.1.2.3/24
| 10.1.2.3/24
| 10.1.2.3/24
| 10.1.2.3/24
| 11.1.2.3/24
| 9.1.2.3/24
Add ipv6 address parsing support to 'inet' and 'cidr' data types. Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
2003-06-25 00:21:24 +02:00
| 10:23::f1/24
| 10:23::ffff/24
| ::4.3.2.1/24
(17 rows)
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
-- check that index works correctly
Add ORDER BY for inet regression, pointed out by Rod Taylor.
2003-01-15 17:35:50 +01:00
CREATE INDEX inet_idx1 ON inet_tbl(i);
SET enable_seqscan TO off;
Back out ORDER BY addition to Inet, for Tom.
2003-01-15 21:01:01 +01:00
SELECT * FROM inet_tbl WHERE i<<'192.168.1.0/24'::cidr;
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
c | i
----------------+------------------
192.168.1.0/24 | 192.168.1.0/25
192.168.1.0/24 | 192.168.1.255/25
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
192.168.1.0/26 | 192.168.1.226
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
(3 rows)
Back out ORDER BY addition to Inet, for Tom.
2003-01-15 21:01:01 +01:00
SELECT * FROM inet_tbl WHERE i<<='192.168.1.0/24'::cidr;
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
c | i
----------------+------------------
192.168.1.0/24 | 192.168.1.0/24
192.168.1.0/24 | 192.168.1.226/24
192.168.1.0/24 | 192.168.1.255/24
192.168.1.0/24 | 192.168.1.0/25
192.168.1.0/24 | 192.168.1.255/25
Update CIDR regresion tests to test for network masks inside the last byte being tested, to catch any future breakage.
2004-10-08 03:45:37 +02:00
192.168.1.0/26 | 192.168.1.226
Make inet/cidr << and <<= operators indexable. From Alex Pilosov <alex@pilosoft.com>.
2001-06-17 04:05:20 +02:00
(6 rows)
Attached is a patch adding following functions: inet(text), cidr(text): convert a text value into inet/cidr set_masklen(inet): set masklen on the inet value Patch also contains regression checks for these functions. Alex Pilosov
2001-06-13 23:09:00 +02:00
Add INET/CIDR operators: and, or, not, plus int8, minus int8, and inet minus inet. Stephen R. van den Berg
2006-02-11 04:32:41 +01:00
SELECT ~i FROM inet_tbl;
?column?
--------------------------------------------
63.87.254.29/24
63.87.254.29
63.87.254.255/24
63.87.254.255/25
63.87.254.0/24
63.87.254.0/25
245.254.253.252/8
245.254.253.252/8
245.254.253.252
245.254.253.252/24
245.254.253.252/16
245.254.253.252/8
244.254.253.252/8
246.254.253.252/8
ffef:ffdc:ffff:ffff:ffff:ffff:ffff:ff0e/64
ffef:ffdc:ffff:ffff:ffff:ffff:ffff:0
ffff:ffff:ffff:ffff:ffff:ffff:fbfc:fdfe/24
(17 rows)
SELECT i & c FROM inet_tbl;
?column?
----------------
192.168.1.0/24
192.168.1.0
192.168.1.0/24
192.168.1.0/25
192.168.1.0/24
192.168.1.0/25
10.0.0.0/8
10.0.0.0
10.1.2.3
10.1.2.0/24
10.1.0.0/16
10.0.0.0/8
10.0.0.0/8
8.0.0.0/8
10:23::f1
10:23::8000
::0.2.2.0
(17 rows)
SELECT i | c FROM inet_tbl;
?column?
------------------
192.168.1.226/24
192.168.1.226
192.168.1.0/24
192.168.1.0/25
192.168.1.255/24
192.168.1.255/25
10.1.2.3/8
10.1.2.3
10.1.2.3
10.1.2.3/24
10.1.2.3/16
10.1.2.3/8
11.1.2.3/8
11.1.2.3/8
10:23::f1
10:23::ffff
::ffff:5.3.3.5
(17 rows)
SELECT i + 500 FROM inet_tbl;
?column?
------------------
192.168.4.214/24
192.168.4.214
192.168.3.244/24
192.168.3.244/25
192.168.4.243/24
192.168.4.243/25
10.1.4.247/8
10.1.4.247/8
10.1.4.247
10.1.4.247/24
10.1.4.247/16
10.1.4.247/8
11.1.4.247/8
9.1.4.247/8
10:23::3e5/64
10:23::1:2f3
::4.3.4.245/24
(17 rows)
SELECT i - 500 FROM inet_tbl;
?column?
--------------------
192.168.255.238/24
192.168.255.238
192.168.255.12/24
192.168.255.12/25
192.168.0.11/24
192.168.0.11/25
10.1.0.15/8
10.1.0.15/8
10.1.0.15
10.1.0.15/24
10.1.0.15/16
10.1.0.15/8
11.1.0.15/8
9.1.0.15/8
10:23::fefd/64
10:23::fe0b
::4.3.0.13/24
(17 rows)
SELECT i - c FROM inet_tbl;
?column?
------------------
226
226
0
0
255
255
66051
66051
0
3
515
66051
16843267
-16711165
0
32767
-281470631346435
(17 rows)
Add ORDER BY for inet regression, pointed out by Rod Taylor.
2003-01-15 17:35:50 +01:00
SET enable_seqscan TO on;
DROP INDEX inet_idx1;