sharpetronics/PostgreSQL
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-31 00:03:57 -04:00
Code Issues Projects Releases Wiki Activity

Improve opr_sanity regression test to check oprltcmpop and opgtcmpop

Browse Source 
mergejoin links.
This commit is contained in:
Tom Lane 2002-09-05 20:23:19 +00:00
parent f4003816f5
commit b73d8d22f7
2 changed files with 82 additions and 58 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
src/test/regress/expected/opr_sanity.out
View File

@ -316,9 +316,13 @@ WHERE p1.oprnegate = p2.oid AND
(0 rows) (0 rows)
-- Look for mergejoin operators that don't match their links. -- Look for mergejoin operators that don't match their links.
-- A mergejoin link leads from an '=' operator to the -- An lsortop/rsortop link leads from an '=' operator to the
-- sort operator ('<' operator) that's appropriate for -- sort operator ('<' operator) that's appropriate for
-- its left-side or right-side data type. -- its left-side or right-side data type.
-- An ltcmpop/gtcmpop link leads from an '=' operator to the
-- '<' or '>' operator of the same input datatypes.
-- (If the '=' operator has identical L and R input datatypes,
-- then lsortop, rsortop, and ltcmpop are all the same operator.)
SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
FROM pg_operator AS p1, pg_operator AS p2 FROM pg_operator AS p1, pg_operator AS p2
WHERE p1.oprlsortop = p2.oid AND WHERE p1.oprlsortop = p2.oid AND
@ -327,8 +331,7 @@ WHERE p1.oprlsortop = p2.oid AND
p1.oprleft != p2.oprleft OR p1.oprleft != p2.oprleft OR
p1.oprleft != p2.oprright OR p1.oprleft != p2.oprright OR
p1.oprresult != 'bool'::regtype OR p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype OR p2.oprresult != 'bool'::regtype);
p1.oprrsortop = 0);
oid | oprcode | oid | oprcode oid | oprcode | oid | oprcode
-----+---------+-----+--------- -----+---------+-----+---------
(0 rows) (0 rows)
@ -341,17 +344,49 @@ WHERE p1.oprrsortop = p2.oid AND
p1.oprright != p2.oprleft OR p1.oprright != p2.oprleft OR
p1.oprright != p2.oprright OR p1.oprright != p2.oprright OR
p1.oprresult != 'bool'::regtype OR p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype OR p2.oprresult != 'bool'::regtype);
p1.oprlsortop = 0);
oid | oprcode | oid | oprcode oid | oprcode | oid | oprcode
-----+---------+-----+--------- -----+---------+-----+---------
(0 rows) (0 rows)
-- A mergejoinable = operator must have a commutator (usually itself) SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
-- as well as corresponding < and > operators. Note that the "corresponding" FROM pg_operator AS p1, pg_operator AS p2
-- operators have the same L and R input datatypes as the = operator, WHERE p1.oprltcmpop = p2.oid AND
-- whereas the operators linked to by oprlsortop and oprrsortop have input (p1.oprname != '=' OR p2.oprname != '<' OR
-- datatypes L,L and R,R respectively. p1.oprkind != 'b' OR p2.oprkind != 'b' OR
p1.oprleft != p2.oprleft OR
p1.oprright != p2.oprright OR
p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype);
oid | oprcode | oid | oprcode
-----+---------+-----+---------
(0 rows)
SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
FROM pg_operator AS p1, pg_operator AS p2
WHERE p1.oprgtcmpop = p2.oid AND
(p1.oprname != '=' OR p2.oprname != '>' OR
p1.oprkind != 'b' OR p2.oprkind != 'b' OR
p1.oprleft != p2.oprleft OR
p1.oprright != p2.oprright OR
p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype);
oid | oprcode | oid | oprcode
-----+---------+-----+---------
(0 rows)
-- Make sure all four links are specified if any are.
SELECT p1.oid, p1.oprcode
FROM pg_operator AS p1
WHERE NOT ((oprlsortop = 0 AND oprrsortop = 0 AND
oprltcmpop = 0 AND oprgtcmpop = 0) OR
(oprlsortop != 0 AND oprrsortop != 0 AND
oprltcmpop != 0 AND oprgtcmpop != 0));
oid | oprcode
-----+---------
(0 rows)
-- A mergejoinable = operator must have a commutator (usually itself).
SELECT p1.oid, p1.oprname FROM pg_operator AS p1 SELECT p1.oid, p1.oprname FROM pg_operator AS p1
WHERE p1.oprlsortop != 0 AND WHERE p1.oprlsortop != 0 AND
p1.oprcom = 0; p1.oprcom = 0;
@ -359,28 +394,6 @@ WHERE p1.oprlsortop != 0 AND
-----+--------- -----+---------
(0 rows) (0 rows)
SELECT p1.oid, p1.oprname FROM pg_operator AS p1
WHERE p1.oprlsortop != 0 AND NOT
EXISTS(SELECT 1 FROM pg_operator AS p2 WHERE
p2.oprname = '<' AND
p2.oprleft = p1.oprleft AND
p2.oprright = p1.oprright AND
p2.oprkind = 'b');
oid | oprname
-----+---------
(0 rows)
SELECT p1.oid, p1.oprname FROM pg_operator AS p1
WHERE p1.oprlsortop != 0 AND NOT
EXISTS(SELECT 1 FROM pg_operator AS p2 WHERE
p2.oprname = '>' AND
p2.oprleft = p1.oprleft AND
p2.oprright = p1.oprright AND
p2.oprkind = 'b');
oid | oprname
-----+---------
(0 rows)
-- Mergejoinable operators across datatypes must come in closed sets, that -- Mergejoinable operators across datatypes must come in closed sets, that
-- is if you provide int2 = int4 and int4 = int8 then you must also provide -- is if you provide int2 = int4 and int4 = int8 then you must also provide
-- int2 = int8 (and commutators of all these). This is necessary because -- int2 = int8 (and commutators of all these). This is necessary because

63
src/test/regress/sql/opr_sanity.sql
View File

@ -259,9 +259,13 @@ WHERE p1.oprnegate = p2.oid AND
p1.oid = p2.oid); p1.oid = p2.oid);
-- Look for mergejoin operators that don't match their links. -- Look for mergejoin operators that don't match their links.
-- A mergejoin link leads from an '=' operator to the -- An lsortop/rsortop link leads from an '=' operator to the
-- sort operator ('<' operator) that's appropriate for -- sort operator ('<' operator) that's appropriate for
-- its left-side or right-side data type. -- its left-side or right-side data type.
-- An ltcmpop/gtcmpop link leads from an '=' operator to the
-- '<' or '>' operator of the same input datatypes.
-- (If the '=' operator has identical L and R input datatypes,
-- then lsortop, rsortop, and ltcmpop are all the same operator.)
SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
FROM pg_operator AS p1, pg_operator AS p2 FROM pg_operator AS p1, pg_operator AS p2
@ -271,8 +275,7 @@ WHERE p1.oprlsortop = p2.oid AND
p1.oprleft != p2.oprleft OR p1.oprleft != p2.oprleft OR
p1.oprleft != p2.oprright OR p1.oprleft != p2.oprright OR
p1.oprresult != 'bool'::regtype OR p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype OR p2.oprresult != 'bool'::regtype);
p1.oprrsortop = 0);
SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
FROM pg_operator AS p1, pg_operator AS p2 FROM pg_operator AS p1, pg_operator AS p2
@ -282,35 +285,43 @@ WHERE p1.oprrsortop = p2.oid AND
p1.oprright != p2.oprleft OR p1.oprright != p2.oprleft OR
p1.oprright != p2.oprright OR p1.oprright != p2.oprright OR
p1.oprresult != 'bool'::regtype OR p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype OR p2.oprresult != 'bool'::regtype);
p1.oprlsortop = 0);
-- A mergejoinable = operator must have a commutator (usually itself) SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
-- as well as corresponding < and > operators. Note that the "corresponding" FROM pg_operator AS p1, pg_operator AS p2
-- operators have the same L and R input datatypes as the = operator, WHERE p1.oprltcmpop = p2.oid AND
-- whereas the operators linked to by oprlsortop and oprrsortop have input (p1.oprname != '=' OR p2.oprname != '<' OR
-- datatypes L,L and R,R respectively. p1.oprkind != 'b' OR p2.oprkind != 'b' OR
p1.oprleft != p2.oprleft OR
p1.oprright != p2.oprright OR
p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype);
SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
FROM pg_operator AS p1, pg_operator AS p2
WHERE p1.oprgtcmpop = p2.oid AND
(p1.oprname != '=' OR p2.oprname != '>' OR
p1.oprkind != 'b' OR p2.oprkind != 'b' OR
p1.oprleft != p2.oprleft OR
p1.oprright != p2.oprright OR
p1.oprresult != 'bool'::regtype OR
p2.oprresult != 'bool'::regtype);
-- Make sure all four links are specified if any are.
SELECT p1.oid, p1.oprcode
FROM pg_operator AS p1
WHERE NOT ((oprlsortop = 0 AND oprrsortop = 0 AND
oprltcmpop = 0 AND oprgtcmpop = 0) OR
(oprlsortop != 0 AND oprrsortop != 0 AND
oprltcmpop != 0 AND oprgtcmpop != 0));
-- A mergejoinable = operator must have a commutator (usually itself).
SELECT p1.oid, p1.oprname FROM pg_operator AS p1 SELECT p1.oid, p1.oprname FROM pg_operator AS p1
WHERE p1.oprlsortop != 0 AND WHERE p1.oprlsortop != 0 AND
p1.oprcom = 0; p1.oprcom = 0;
SELECT p1.oid, p1.oprname FROM pg_operator AS p1
WHERE p1.oprlsortop != 0 AND NOT
EXISTS(SELECT 1 FROM pg_operator AS p2 WHERE
p2.oprname = '<' AND
p2.oprleft = p1.oprleft AND
p2.oprright = p1.oprright AND
p2.oprkind = 'b');
SELECT p1.oid, p1.oprname FROM pg_operator AS p1
WHERE p1.oprlsortop != 0 AND NOT
EXISTS(SELECT 1 FROM pg_operator AS p2 WHERE
p2.oprname = '>' AND
p2.oprleft = p1.oprleft AND
p2.oprright = p1.oprright AND
p2.oprkind = 'b');
-- Mergejoinable operators across datatypes must come in closed sets, that -- Mergejoinable operators across datatypes must come in closed sets, that
-- is if you provide int2 = int4 and int4 = int8 then you must also provide -- is if you provide int2 = int4 and int4 = int8 then you must also provide
-- int2 = int8 (and commutators of all these). This is necessary because -- int2 = int8 (and commutators of all these). This is necessary because