postgresql/contrib/btree_gist/sql/cidr.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 gist_cidr_ops );

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;
New version. Add support for int2, int8, float4, float8, timestamp with/without time zone, time with/without time zone, date, interval, oid, money and macaddr, char, varchar/text, bytea, numeric, bit, varbit, inet/cidr types for GiST 2004-05-28 06:43:32 -04:00			`-- 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 btree_gist v1.9, in which inet/cidr opclasses aren't default. btree_gist's gist_inet_ops and gist_cidr_ops opclasses are fundamentally broken: they rely on an approximate representation of the inet values and hence sometimes miss rows they should return. We want to eventually get rid of them altogether, but as the first step on that journey, we should mark them not-opcdefault. To do that, roll up the preceding deltas since 1.2 into a new base script btree_gist--1.9.sql. This will allow installing 1.9 without going through a transient situation where gist_inet_ops and gist_cidr_ops are marked as opcdefault; trying to create them that way will fail if there's already a matching default opclass in the core system. Additionally provide btree_gist--1.8--1.9.sql, so that a database that's been pg_upgraded from an older version can be migrated to 1.9. I noted along the way that commit 57e3c5160 had missed marking the gist_bool_ops support functions as PARALLEL SAFE. While that probably has little harmful effect (since AFAIK we don't check that when calling index support functions), this seems like a good time to make things consistent. Readers will also note that I removed the former habit of installing some opclass operators/functions with ALTER OPERATOR FAMILY, instead just rolling them all into the CREATE OPERATOR CLASS steps. The comment in btree_gist--1.2.sql that it's necessary to use ALTER for pg_upgrade reproducibility has been obsolete since we invented the amadjustmembers infrastructure. Nowadays, gistadjustmembers will force all operators and non-required support functions to have "soft" opfamily dependencies, regardless of whether they are installed by CREATE or ALTER. Author: Tom Lane <tgl@sss.pgh.pa.us> Reviewed-by: Matthias van de Meent <boekewurm+postgres@gmail.com> Reviewed-by: Heikki Linnakangas <hlinnaka@iki.fi> Discussion: https://postgr.es/m/2483812.1754072263@sss.pgh.pa.us 2026-01-08 13:56:08 -05:00			`CREATE INDEX cidridx ON cidrtmp USING gist ( a gist_cidr_ops );`
New version. Add support for int2, int8, float4, float8, timestamp with/without time zone, time with/without time zone, date, interval, oid, money and macaddr, char, varchar/text, bytea, numeric, bit, varbit, inet/cidr types for GiST 2004-05-28 06:43:32 -04:00
			`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;`