3 -- Sanity checks for common errors in making operator/procedure system tables:
4 -- pg_operator, pg_proc, pg_cast, pg_aggregate, pg_am, pg_amop, pg_amproc, pg_opclass.
6 -- None of the SELECTs here should ever find any matching entries,
7 -- so the expected output is easy to maintain ;-).
8 -- A test failure indicates someone messed up an entry in the system tables.
10 -- NB: we assume the oidjoins test will have caught any dangling links,
11 -- that is OID or REGPROC fields that are not zero and do not match some
12 -- row in the linked-to table. However, if we want to enforce that a link
13 -- field can't be 0, we have to check it here.
15 -- NB: run this test earlier than the create_operator test, because
16 -- that test creates some bogus operators...
19 -- Helper functions to deal with cases where binary-coercible matches are
22 -- This should match IsBinaryCoercible() in parse_coerce.c.
23 create function binary_coercible(oid, oid) returns bool as
25 EXISTS(select 1 from pg_cast where
26 castsource = $1 and casttarget = $2 and
27 castfunc = 0 and castcontext = ''i'')'
30 -- This one ignores castcontext, so it considers only physical equivalence
31 -- and not whether the coercion can be invoked implicitly.
32 create function physically_coercible(oid, oid) returns bool as
34 EXISTS(select 1 from pg_cast where
35 castsource = $1 and casttarget = $2 and
39 -- **************** pg_proc ****************
41 -- Look for illegal values in pg_proc fields.
42 -- NOTE: in reality pronargs could be more than 10, but I'm too lazy to put
43 -- a larger number of proargtypes check clauses in here. If we ever have
44 -- more-than-10-arg functions in the standard catalogs, extend this query.
46 SELECT p1.oid, p1.proname
48 WHERE p1.prolang = 0 OR p1.prorettype = 0 OR
49 p1.pronargs < 0 OR p1.pronargs > 10 OR
50 (p1.proargtypes[0] = 0 AND p1.pronargs > 0) OR
51 (p1.proargtypes[1] = 0 AND p1.pronargs > 1) OR
52 (p1.proargtypes[2] = 0 AND p1.pronargs > 2) OR
53 (p1.proargtypes[3] = 0 AND p1.pronargs > 3) OR
54 (p1.proargtypes[4] = 0 AND p1.pronargs > 4) OR
55 (p1.proargtypes[5] = 0 AND p1.pronargs > 5) OR
56 (p1.proargtypes[6] = 0 AND p1.pronargs > 6) OR
57 (p1.proargtypes[7] = 0 AND p1.pronargs > 7) OR
58 (p1.proargtypes[8] = 0 AND p1.pronargs > 8) OR
59 (p1.proargtypes[9] = 0 AND p1.pronargs > 9);
61 -- Look for conflicting proc definitions (same names and input datatypes).
62 -- (This test should be dead code now that we have the unique index
63 -- pg_proc_proname_narg_type_index, but I'll leave it in anyway.)
65 SELECT p1.oid, p1.proname, p2.oid, p2.proname
66 FROM pg_proc AS p1, pg_proc AS p2
67 WHERE p1.oid != p2.oid AND
68 p1.proname = p2.proname AND
69 p1.pronargs = p2.pronargs AND
70 p1.proargtypes = p2.proargtypes;
72 -- Considering only built-in procs (prolang = 12), look for multiple uses
73 -- of the same internal function (ie, matching prosrc fields). It's OK to
74 -- have several entries with different pronames for the same internal function,
75 -- but conflicts in the number of arguments and other critical items should
78 SELECT p1.oid, p1.proname, p2.oid, p2.proname
79 FROM pg_proc AS p1, pg_proc AS p2
80 WHERE p1.oid != p2.oid AND
81 p1.prosrc = p2.prosrc AND
82 p1.prolang = 12 AND p2.prolang = 12 AND
83 (p1.prolang != p2.prolang OR
84 p1.proisagg != p2.proisagg OR
85 p1.prosecdef != p2.prosecdef OR
86 p1.proisstrict != p2.proisstrict OR
87 p1.proretset != p2.proretset OR
88 p1.provolatile != p2.provolatile OR
89 p1.pronargs != p2.pronargs);
91 -- Look for uses of different type OIDs in the argument/result type fields
92 -- for different aliases of the same built-in function.
93 -- This indicates that the types are being presumed to be binary-equivalent,
94 -- or that the built-in function is prepared to deal with different types.
95 -- That's not wrong, necessarily, but we make lists of all the types being
96 -- so treated. Note that the expected output of this part of the test will
97 -- need to be modified whenever new pairs of types are made binary-equivalent,
98 -- or when new polymorphic built-in functions are added!
99 -- Note: ignore aggregate functions here, since they all point to the same
100 -- dummy built-in function.
102 SELECT DISTINCT p1.prorettype, p2.prorettype
103 FROM pg_proc AS p1, pg_proc AS p2
104 WHERE p1.oid != p2.oid AND
105 p1.prosrc = p2.prosrc AND
106 p1.prolang = 12 AND p2.prolang = 12 AND
107 NOT p1.proisagg AND NOT p2.proisagg AND
108 (p1.prorettype < p2.prorettype);
110 SELECT DISTINCT p1.proargtypes[0], p2.proargtypes[0]
111 FROM pg_proc AS p1, pg_proc AS p2
112 WHERE p1.oid != p2.oid AND
113 p1.prosrc = p2.prosrc AND
114 p1.prolang = 12 AND p2.prolang = 12 AND
115 NOT p1.proisagg AND NOT p2.proisagg AND
116 (p1.proargtypes[0] < p2.proargtypes[0]);
118 SELECT DISTINCT p1.proargtypes[1], p2.proargtypes[1]
119 FROM pg_proc AS p1, pg_proc AS p2
120 WHERE p1.oid != p2.oid AND
121 p1.prosrc = p2.prosrc AND
122 p1.prolang = 12 AND p2.prolang = 12 AND
123 NOT p1.proisagg AND NOT p2.proisagg AND
124 (p1.proargtypes[1] < p2.proargtypes[1]);
126 SELECT DISTINCT p1.proargtypes[2], p2.proargtypes[2]
127 FROM pg_proc AS p1, pg_proc AS p2
128 WHERE p1.oid != p2.oid AND
129 p1.prosrc = p2.prosrc AND
130 p1.prolang = 12 AND p2.prolang = 12 AND
131 NOT p1.proisagg AND NOT p2.proisagg AND
132 (p1.proargtypes[2] < p2.proargtypes[2]);
134 SELECT DISTINCT p1.proargtypes[3], p2.proargtypes[3]
135 FROM pg_proc AS p1, pg_proc AS p2
136 WHERE p1.oid != p2.oid AND
137 p1.prosrc = p2.prosrc AND
138 p1.prolang = 12 AND p2.prolang = 12 AND
139 NOT p1.proisagg AND NOT p2.proisagg AND
140 (p1.proargtypes[3] < p2.proargtypes[3]);
142 SELECT DISTINCT p1.proargtypes[4], p2.proargtypes[4]
143 FROM pg_proc AS p1, pg_proc AS p2
144 WHERE p1.oid != p2.oid AND
145 p1.prosrc = p2.prosrc AND
146 p1.prolang = 12 AND p2.prolang = 12 AND
147 NOT p1.proisagg AND NOT p2.proisagg AND
148 (p1.proargtypes[4] < p2.proargtypes[4]);
150 SELECT DISTINCT p1.proargtypes[5], p2.proargtypes[5]
151 FROM pg_proc AS p1, pg_proc AS p2
152 WHERE p1.oid != p2.oid AND
153 p1.prosrc = p2.prosrc AND
154 p1.prolang = 12 AND p2.prolang = 12 AND
155 NOT p1.proisagg AND NOT p2.proisagg AND
156 (p1.proargtypes[5] < p2.proargtypes[5]);
158 SELECT DISTINCT p1.proargtypes[6], p2.proargtypes[6]
159 FROM pg_proc AS p1, pg_proc AS p2
160 WHERE p1.oid != p2.oid AND
161 p1.prosrc = p2.prosrc AND
162 p1.prolang = 12 AND p2.prolang = 12 AND
163 NOT p1.proisagg AND NOT p2.proisagg AND
164 (p1.proargtypes[6] < p2.proargtypes[6]);
166 SELECT DISTINCT p1.proargtypes[7], p2.proargtypes[7]
167 FROM pg_proc AS p1, pg_proc AS p2
168 WHERE p1.oid != p2.oid AND
169 p1.prosrc = p2.prosrc AND
170 p1.prolang = 12 AND p2.prolang = 12 AND
171 NOT p1.proisagg AND NOT p2.proisagg AND
172 (p1.proargtypes[7] < p2.proargtypes[7]);
174 -- Look for functions that return type "internal" and do not have any
175 -- "internal" argument. Such a function would be a security hole since
176 -- it might be used to call an internal function from an SQL command.
177 -- As of 7.3 this query should find only internal_in.
179 SELECT p1.oid, p1.proname
181 WHERE p1.prorettype = 'internal'::regtype AND NOT
182 ('(' || oidvectortypes(p1.proargtypes) || ')') ~ '[^a-z0-9_]internal[^a-z0-9_]';
185 -- **************** pg_cast ****************
187 -- Look for casts from and to the same type. This is not harmful, but
188 -- useless. Also catch bogus values in pg_cast columns (other than
189 -- cases detected by oidjoins test).
193 WHERE castsource = casttarget OR castsource = 0 OR casttarget = 0
194 OR castcontext NOT IN ('e', 'a', 'i');
196 -- Look for cast functions that don't have the right signature. The
197 -- argument and result types in pg_proc must be the same as, or binary
198 -- compatible with, what it says in pg_cast.
201 FROM pg_cast c, pg_proc p
202 WHERE c.castfunc = p.oid AND
204 OR NOT binary_coercible(c.castsource, p.proargtypes[0])
205 OR NOT binary_coercible(p.prorettype, c.casttarget));
207 -- Look for binary compatible casts that do not have the reverse
208 -- direction registered as well, or where the reverse direction is not
209 -- also binary compatible. This is legal, but usually not intended.
211 -- As of 7.4, this finds the casts from text and varchar to bpchar, because
212 -- those are binary-compatible while the reverse way goes through rtrim().
216 WHERE c.castfunc = 0 AND
217 NOT EXISTS (SELECT 1 FROM pg_cast k
218 WHERE k.castfunc = 0 AND
219 k.castsource = c.casttarget AND
220 k.casttarget = c.castsource);
222 -- **************** pg_operator ****************
224 -- Look for illegal values in pg_operator fields.
226 SELECT p1.oid, p1.oprname
227 FROM pg_operator as p1
228 WHERE (p1.oprkind != 'b' AND p1.oprkind != 'l' AND p1.oprkind != 'r') OR
229 p1.oprresult = 0 OR p1.oprcode = 0;
231 -- Look for missing or unwanted operand types
233 SELECT p1.oid, p1.oprname
234 FROM pg_operator as p1
235 WHERE (p1.oprleft = 0 and p1.oprkind != 'l') OR
236 (p1.oprleft != 0 and p1.oprkind = 'l') OR
237 (p1.oprright = 0 and p1.oprkind != 'r') OR
238 (p1.oprright != 0 and p1.oprkind = 'r');
240 -- Look for conflicting operator definitions (same names and input datatypes).
242 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
243 FROM pg_operator AS p1, pg_operator AS p2
244 WHERE p1.oid != p2.oid AND
245 p1.oprname = p2.oprname AND
246 p1.oprkind = p2.oprkind AND
247 p1.oprleft = p2.oprleft AND
248 p1.oprright = p2.oprright;
250 -- Look for commutative operators that don't commute.
251 -- DEFINITIONAL NOTE: If A.oprcom = B, then x A y has the same result as y B x.
252 -- We expect that B will always say that B.oprcom = A as well; that's not
253 -- inherently essential, but it would be inefficient not to mark it so.
255 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
256 FROM pg_operator AS p1, pg_operator AS p2
257 WHERE p1.oprcom = p2.oid AND
258 (p1.oprkind != 'b' OR
259 p1.oprleft != p2.oprright OR
260 p1.oprright != p2.oprleft OR
261 p1.oprresult != p2.oprresult OR
262 p1.oid != p2.oprcom);
264 -- Look for negatory operators that don't agree.
265 -- DEFINITIONAL NOTE: If A.oprnegate = B, then both A and B must yield
266 -- boolean results, and (x A y) == ! (x B y), or the equivalent for
267 -- single-operand operators.
268 -- We expect that B will always say that B.oprnegate = A as well; that's not
269 -- inherently essential, but it would be inefficient not to mark it so.
270 -- Also, A and B had better not be the same operator.
272 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
273 FROM pg_operator AS p1, pg_operator AS p2
274 WHERE p1.oprnegate = p2.oid AND
275 (p1.oprkind != p2.oprkind OR
276 p1.oprleft != p2.oprleft OR
277 p1.oprright != p2.oprright OR
278 p1.oprresult != 'bool'::regtype OR
279 p2.oprresult != 'bool'::regtype OR
280 p1.oid != p2.oprnegate OR
283 -- Look for mergejoin operators that don't match their links.
284 -- An lsortop/rsortop link leads from an '=' operator to the
285 -- sort operator ('<' operator) that's appropriate for
286 -- its left-side or right-side data type.
287 -- An ltcmpop/gtcmpop link leads from an '=' operator to the
288 -- '<' or '>' operator of the same input datatypes.
289 -- (If the '=' operator has identical L and R input datatypes,
290 -- then lsortop, rsortop, and ltcmpop are all the same operator.)
292 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
293 FROM pg_operator AS p1, pg_operator AS p2
294 WHERE p1.oprlsortop = p2.oid AND
295 (p1.oprname NOT IN ('=', '~=~') OR p2.oprname NOT IN ('<', '~<~') OR
296 p1.oprkind != 'b' OR p2.oprkind != 'b' OR
297 p1.oprleft != p2.oprleft OR
298 p1.oprleft != p2.oprright OR
299 p1.oprresult != 'bool'::regtype OR
300 p2.oprresult != 'bool'::regtype);
302 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
303 FROM pg_operator AS p1, pg_operator AS p2
304 WHERE p1.oprrsortop = p2.oid AND
305 (p1.oprname NOT IN ('=', '~=~') OR p2.oprname NOT IN ('<', '~<~') OR
306 p1.oprkind != 'b' OR p2.oprkind != 'b' OR
307 p1.oprright != p2.oprleft OR
308 p1.oprright != p2.oprright OR
309 p1.oprresult != 'bool'::regtype OR
310 p2.oprresult != 'bool'::regtype);
312 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
313 FROM pg_operator AS p1, pg_operator AS p2
314 WHERE p1.oprltcmpop = p2.oid AND
315 (p1.oprname NOT IN ('=', '~=~') OR p2.oprname NOT IN ('<', '~<~') OR
316 p1.oprkind != 'b' OR p2.oprkind != 'b' OR
317 p1.oprleft != p2.oprleft OR
318 p1.oprright != p2.oprright OR
319 p1.oprresult != 'bool'::regtype OR
320 p2.oprresult != 'bool'::regtype);
322 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
323 FROM pg_operator AS p1, pg_operator AS p2
324 WHERE p1.oprgtcmpop = p2.oid AND
325 (p1.oprname NOT IN ('=', '~=~') OR p2.oprname NOT IN ('>', '~>~') OR
326 p1.oprkind != 'b' OR p2.oprkind != 'b' OR
327 p1.oprleft != p2.oprleft OR
328 p1.oprright != p2.oprright OR
329 p1.oprresult != 'bool'::regtype OR
330 p2.oprresult != 'bool'::regtype);
332 -- Make sure all four links are specified if any are.
334 SELECT p1.oid, p1.oprcode
335 FROM pg_operator AS p1
336 WHERE NOT ((oprlsortop = 0 AND oprrsortop = 0 AND
337 oprltcmpop = 0 AND oprgtcmpop = 0) OR
338 (oprlsortop != 0 AND oprrsortop != 0 AND
339 oprltcmpop != 0 AND oprgtcmpop != 0));
341 -- A mergejoinable = operator must have a commutator (usually itself).
343 SELECT p1.oid, p1.oprname FROM pg_operator AS p1
344 WHERE p1.oprlsortop != 0 AND
347 -- Mergejoinable operators across datatypes must come in closed sets, that
348 -- is if you provide int2 = int4 and int4 = int8 then you must also provide
349 -- int2 = int8 (and commutators of all these). This is necessary because
350 -- the planner tries to deduce additional qual clauses from transitivity
351 -- of mergejoinable operators. If there are clauses int2var = int4var and
352 -- int4var = int8var, the planner will deduce int2var = int8var ... and it
353 -- had better have a way to represent it.
355 SELECT p1.oid, p2.oid FROM pg_operator AS p1, pg_operator AS p2
356 WHERE p1.oprlsortop != p1.oprrsortop AND
357 p1.oprrsortop = p2.oprlsortop AND
358 p2.oprlsortop != p2.oprrsortop AND
359 NOT EXISTS (SELECT 1 FROM pg_operator p3 WHERE
360 p3.oprlsortop = p1.oprlsortop AND p3.oprrsortop = p2.oprrsortop);
363 -- Hashing only works on simple equality operators "type = sametype",
364 -- since the hash itself depends on the bitwise representation of the type.
365 -- Check that allegedly hashable operators look like they might be "=".
367 SELECT p1.oid, p1.oprname
368 FROM pg_operator AS p1
369 WHERE p1.oprcanhash AND NOT
370 (p1.oprkind = 'b' AND p1.oprresult = 'bool'::regtype AND
371 p1.oprleft = p1.oprright AND p1.oprname IN ('=', '~=~') AND
374 -- In 6.5 we accepted hashable array equality operators when the array element
375 -- type is hashable. However, what we actually need to make hashjoin work on
376 -- an array is a hashable element type *and* no padding between elements in
377 -- the array storage (or, perhaps, guaranteed-zero padding). Currently,
378 -- since the padding code in arrayfuncs.c is pretty bogus, it seems safest
379 -- to just forbid hashjoin on array equality ops.
380 -- This should be reconsidered someday.
382 -- -- Look for array equality operators that are hashable when the underlying
383 -- -- type is not, or vice versa. This is presumably bogus.
385 -- SELECT p1.oid, p1.oprcanhash, p2.oid, p2.oprcanhash, t1.typname, t2.typname
386 -- FROM pg_operator AS p1, pg_operator AS p2, pg_type AS t1, pg_type AS t2
387 -- WHERE p1.oprname = '=' AND p1.oprleft = p1.oprright AND
388 -- p2.oprname = '=' AND p2.oprleft = p2.oprright AND
389 -- p1.oprleft = t1.oid AND p2.oprleft = t2.oid AND t1.typelem = t2.oid AND
390 -- p1.oprcanhash != p2.oprcanhash;
392 -- Substitute check: forbid hashable array ops, period.
393 SELECT p1.oid, p1.oprname
394 FROM pg_operator AS p1, pg_proc AS p2
395 WHERE p1.oprcanhash AND p1.oprcode = p2.oid AND p2.proname = 'array_eq';
397 -- Hashable operators should appear as members of hash index opclasses.
399 SELECT p1.oid, p1.oprname
400 FROM pg_operator AS p1
401 WHERE p1.oprcanhash AND NOT EXISTS
402 (SELECT 1 FROM pg_opclass op JOIN pg_amop p ON op.oid = amopclaid
403 WHERE opcamid = (SELECT oid FROM pg_am WHERE amname = 'hash') AND
407 -- Check that each operator defined in pg_operator matches its oprcode entry
408 -- in pg_proc. Easiest to do this separately for each oprkind.
410 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
411 FROM pg_operator AS p1, pg_proc AS p2
412 WHERE p1.oprcode = p2.oid AND
415 OR NOT binary_coercible(p2.prorettype, p1.oprresult)
416 OR NOT binary_coercible(p1.oprleft, p2.proargtypes[0])
417 OR NOT binary_coercible(p1.oprright, p2.proargtypes[1]));
419 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
420 FROM pg_operator AS p1, pg_proc AS p2
421 WHERE p1.oprcode = p2.oid AND
424 OR NOT binary_coercible(p2.prorettype, p1.oprresult)
425 OR NOT binary_coercible(p1.oprright, p2.proargtypes[0])
428 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
429 FROM pg_operator AS p1, pg_proc AS p2
430 WHERE p1.oprcode = p2.oid AND
433 OR NOT binary_coercible(p2.prorettype, p1.oprresult)
434 OR NOT binary_coercible(p1.oprleft, p2.proargtypes[0])
435 OR p1.oprright != 0);
437 -- If the operator is mergejoinable or hashjoinable, its underlying function
438 -- should not be volatile.
440 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
441 FROM pg_operator AS p1, pg_proc AS p2
442 WHERE p1.oprcode = p2.oid AND
443 (p1.oprlsortop != 0 OR p1.oprcanhash) AND
444 p2.provolatile = 'v';
446 -- If oprrest is set, the operator must return boolean,
447 -- and it must link to a proc with the right signature
448 -- to be a restriction selectivity estimator.
449 -- The proc signature we want is: float8 proc(internal, oid, internal, int4)
451 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
452 FROM pg_operator AS p1, pg_proc AS p2
453 WHERE p1.oprrest = p2.oid AND
454 (p1.oprresult != 'bool'::regtype OR
455 p2.prorettype != 'float8'::regtype OR p2.proretset OR
457 p2.proargtypes[0] != 'internal'::regtype OR
458 p2.proargtypes[1] != 'oid'::regtype OR
459 p2.proargtypes[2] != 'internal'::regtype OR
460 p2.proargtypes[3] != 'int4'::regtype);
462 -- If oprjoin is set, the operator must be a binary boolean op,
463 -- and it must link to a proc with the right signature
464 -- to be a join selectivity estimator.
465 -- The proc signature we want is: float8 proc(internal, oid, internal, int2)
467 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
468 FROM pg_operator AS p1, pg_proc AS p2
469 WHERE p1.oprjoin = p2.oid AND
470 (p1.oprkind != 'b' OR p1.oprresult != 'bool'::regtype OR
471 p2.prorettype != 'float8'::regtype OR p2.proretset OR
473 p2.proargtypes[0] != 'internal'::regtype OR
474 p2.proargtypes[1] != 'oid'::regtype OR
475 p2.proargtypes[2] != 'internal'::regtype OR
476 p2.proargtypes[3] != 'int2'::regtype);
478 -- **************** pg_aggregate ****************
480 -- Look for illegal values in pg_aggregate fields.
482 SELECT ctid, aggfnoid::oid
483 FROM pg_aggregate as p1
484 WHERE aggfnoid = 0 OR aggtransfn = 0 OR aggtranstype = 0;
486 -- Make sure the matching pg_proc entry is sensible, too.
488 SELECT a.aggfnoid::oid, p.proname
489 FROM pg_aggregate as a, pg_proc as p
490 WHERE a.aggfnoid = p.oid AND
491 (NOT p.proisagg OR p.pronargs != 1 OR p.proretset);
493 -- Make sure there are no proisagg pg_proc entries without matches.
498 NOT EXISTS (SELECT 1 FROM pg_aggregate a WHERE a.aggfnoid = p.oid);
500 -- If there is no finalfn then the output type must be the transtype.
502 SELECT a.aggfnoid::oid, p.proname
503 FROM pg_aggregate as a, pg_proc as p
504 WHERE a.aggfnoid = p.oid AND
505 a.aggfinalfn = 0 AND p.prorettype != a.aggtranstype;
507 -- Cross-check transfn against its entry in pg_proc.
508 -- NOTE: use physically_coercible here, not binary_coercible, because
509 -- max and min on abstime are implemented using int4larger/int4smaller.
510 SELECT a.aggfnoid::oid, p.proname, ptr.oid, ptr.proname
511 FROM pg_aggregate AS a, pg_proc AS p, pg_proc AS ptr
512 WHERE a.aggfnoid = p.oid AND
513 a.aggtransfn = ptr.oid AND
515 OR NOT physically_coercible(ptr.prorettype, a.aggtranstype)
516 OR NOT physically_coercible(a.aggtranstype, ptr.proargtypes[0])
517 OR NOT ((ptr.pronargs = 2 AND
518 physically_coercible(p.proargtypes[0], ptr.proargtypes[1]))
520 (ptr.pronargs = 1 AND
521 p.proargtypes[0] = '"any"'::regtype)));
523 -- Cross-check finalfn (if present) against its entry in pg_proc.
525 SELECT a.aggfnoid::oid, p.proname, pfn.oid, pfn.proname
526 FROM pg_aggregate AS a, pg_proc AS p, pg_proc AS pfn
527 WHERE a.aggfnoid = p.oid AND
528 a.aggfinalfn = pfn.oid AND
530 OR NOT binary_coercible(pfn.prorettype, p.prorettype)
532 OR NOT binary_coercible(a.aggtranstype, pfn.proargtypes[0]));
534 -- If transfn is strict then either initval should be non-NULL, or
535 -- input type should match transtype so that the first non-null input
536 -- can be assigned as the state value.
538 SELECT a.aggfnoid::oid, p.proname, ptr.oid, ptr.proname
539 FROM pg_aggregate AS a, pg_proc AS p, pg_proc AS ptr
540 WHERE a.aggfnoid = p.oid AND
541 a.aggtransfn = ptr.oid AND ptr.proisstrict AND
542 a.agginitval IS NULL AND
543 NOT binary_coercible(p.proargtypes[0], a.aggtranstype);
545 -- **************** pg_opclass ****************
547 -- Look for illegal values in pg_opclass fields
550 FROM pg_opclass as p1
551 WHERE p1.opcamid = 0 OR p1.opcintype = 0;
553 -- There should not be multiple entries in pg_opclass with opcdefault true
554 -- and the same opcamid/opcintype combination.
556 SELECT p1.oid, p2.oid
557 FROM pg_opclass AS p1, pg_opclass AS p2
558 WHERE p1.oid != p2.oid AND
559 p1.opcamid = p2.opcamid AND p1.opcintype = p2.opcintype AND
560 p1.opcdefault AND p2.opcdefault;
562 -- **************** pg_amop ****************
564 -- Look for illegal values in pg_amop fields
566 SELECT p1.amopclaid, p1.amopstrategy
568 WHERE p1.amopclaid = 0 OR p1.amopstrategy <= 0 OR p1.amopopr = 0;
570 -- Cross-check amopstrategy index against parent AM
572 SELECT p1.amopclaid, p1.amopopr, p2.oid, p2.amname
573 FROM pg_amop AS p1, pg_am AS p2, pg_opclass AS p3
574 WHERE p1.amopclaid = p3.oid AND p3.opcamid = p2.oid AND
575 p1.amopstrategy > p2.amstrategies;
577 -- Detect missing pg_amop entries: should have as many strategy operators
578 -- as AM expects for each opclass for the AM. When nondefault subtypes are
579 -- present, enforce condition separately for each subtype.
581 SELECT p1.oid, p1.amname, p2.oid, p2.opcname, p3.amopsubtype
582 FROM pg_am AS p1, pg_opclass AS p2, pg_amop AS p3
583 WHERE p2.opcamid = p1.oid AND p3.amopclaid = p2.oid AND
584 p1.amstrategies != (SELECT count(*) FROM pg_amop AS p4
585 WHERE p4.amopclaid = p2.oid AND
586 p4.amopsubtype = p3.amopsubtype);
588 -- Check that amopopr points at a reasonable-looking operator, ie a binary
589 -- operator yielding boolean.
591 SELECT p1.amopclaid, p1.amopopr, p2.oid, p2.oprname
592 FROM pg_amop AS p1, pg_operator AS p2
593 WHERE p1.amopopr = p2.oid AND
594 (p2.oprkind != 'b' OR p2.oprresult != 'bool'::regtype);
596 -- Make a list of all the distinct operator names being used in particular
597 -- strategy slots. This is a bit hokey, since the list might need to change
598 -- in future releases, but it's an effective way of spotting mistakes such as
599 -- swapping two operators within a class.
601 SELECT DISTINCT opcamid, amopstrategy, oprname
602 FROM pg_amop p1 LEFT JOIN pg_opclass p2 ON amopclaid = p2.oid
603 LEFT JOIN pg_operator p3 ON amopopr = p3.oid
606 -- Check that all operators linked to by opclass entries have selectivity
607 -- estimators. This is not absolutely required, but it seems a reasonable
608 -- thing to insist on for all standard datatypes.
610 SELECT p1.amopclaid, p1.amopopr, p2.oid, p2.oprname
611 FROM pg_amop AS p1, pg_operator AS p2
612 WHERE p1.amopopr = p2.oid AND
613 (p2.oprrest = 0 OR p2.oprjoin = 0);
615 -- Check that operator input types match the opclass
616 -- For 7.5, we require that oprleft match opcintype (possibly by coercion).
617 -- When amopsubtype is zero (default), oprright must equal oprleft;
618 -- when amopsubtype is not zero, oprright must equal amopsubtype.
620 SELECT p1.amopclaid, p1.amopopr, p2.oid, p2.oprname, p3.opcname
621 FROM pg_amop AS p1, pg_operator AS p2, pg_opclass AS p3
622 WHERE p1.amopopr = p2.oid AND p1.amopclaid = p3.oid AND
623 NOT binary_coercible(p3.opcintype, p2.oprleft);
625 SELECT p1.amopclaid, p1.amopopr, p2.oid, p2.oprname, p3.opcname
626 FROM pg_amop AS p1, pg_operator AS p2, pg_opclass AS p3
627 WHERE p1.amopopr = p2.oid AND p1.amopclaid = p3.oid AND
628 p1.amopsubtype = 0 AND
629 p2.oprleft != p2.oprright;
631 SELECT p1.amopclaid, p1.amopopr, p2.oid, p2.oprname, p3.opcname
632 FROM pg_amop AS p1, pg_operator AS p2, pg_opclass AS p3
633 WHERE p1.amopopr = p2.oid AND p1.amopclaid = p3.oid AND
634 p1.amopsubtype != 0 AND
635 p1.amopsubtype != p2.oprright;
637 -- **************** pg_amproc ****************
639 -- Look for illegal values in pg_amproc fields
641 SELECT p1.amopclaid, p1.amprocnum
643 WHERE p1.amopclaid = 0 OR p1.amprocnum <= 0 OR p1.amproc = 0;
645 -- Cross-check amprocnum index against parent AM
647 SELECT p1.amopclaid, p1.amprocnum, p2.oid, p2.amname
648 FROM pg_amproc AS p1, pg_am AS p2, pg_opclass AS p3
649 WHERE p1.amopclaid = p3.oid AND p3.opcamid = p2.oid AND
650 p1.amprocnum > p2.amsupport;
652 -- Detect missing pg_amproc entries: should have as many support functions
653 -- as AM expects for each opclass for the AM. When nondefault subtypes are
654 -- present, enforce condition separately for each subtype.
656 SELECT p1.oid, p1.amname, p2.oid, p2.opcname, p3.amprocsubtype
657 FROM pg_am AS p1, pg_opclass AS p2, pg_amproc AS p3
658 WHERE p2.opcamid = p1.oid AND p3.amopclaid = p2.oid AND
659 p1.amsupport != (SELECT count(*) FROM pg_amproc AS p4
660 WHERE p4.amopclaid = p2.oid AND
661 p4.amprocsubtype = p3.amprocsubtype);
663 -- Unfortunately, we can't check the amproc link very well because the
664 -- signature of the function may be different for different support routines
665 -- or different base data types.
666 -- We can check that all the referenced instances of the same support
667 -- routine number take the same number of parameters, but that's about it
668 -- for a general check...
670 SELECT p1.amopclaid, p1.amprocnum,
673 p4.amopclaid, p4.amprocnum,
676 FROM pg_amproc AS p1, pg_proc AS p2, pg_opclass AS p3,
677 pg_amproc AS p4, pg_proc AS p5, pg_opclass AS p6
678 WHERE p1.amopclaid = p3.oid AND p4.amopclaid = p6.oid AND
679 p3.opcamid = p6.opcamid AND p1.amprocnum = p4.amprocnum AND
680 p1.amproc = p2.oid AND p4.amproc = p5.oid AND
681 (p2.proretset OR p5.proretset OR p2.pronargs != p5.pronargs);
683 -- For btree, though, we can do better since we know the support routines
684 -- must be of the form cmp(input, input) returns int4 in the default case
685 -- (subtype = 0), and cmp(input, subtype) returns int4 when subtype != 0.
687 SELECT p1.amopclaid, p1.amprocnum,
690 FROM pg_amproc AS p1, pg_proc AS p2, pg_opclass AS p3
691 WHERE p3.opcamid = (SELECT oid FROM pg_am WHERE amname = 'btree')
692 AND p1.amopclaid = p3.oid AND p1.amproc = p2.oid AND
693 amprocsubtype = 0 AND
699 OR NOT binary_coercible(opcintype, proargtypes[0])
700 OR proargtypes[0] != proargtypes[1]);
702 SELECT p1.amopclaid, p1.amprocnum,
705 FROM pg_amproc AS p1, pg_proc AS p2, pg_opclass AS p3
706 WHERE p3.opcamid = (SELECT oid FROM pg_am WHERE amname = 'btree')
707 AND p1.amopclaid = p3.oid AND p1.amproc = p2.oid AND
708 amprocsubtype != 0 AND
714 OR NOT binary_coercible(opcintype, proargtypes[0])
715 OR proargtypes[1] != amprocsubtype);
717 -- For hash we can also do a little better: the support routines must be
718 -- of the form hash(something) returns int4. Ideally we'd check that the
719 -- opcintype is binary-coercible to the function's input, but there are
720 -- enough cases where that fails that I'll just leave out the check for now.
722 SELECT p1.amopclaid, p1.amprocnum,
725 FROM pg_amproc AS p1, pg_proc AS p2, pg_opclass AS p3
726 WHERE p3.opcamid = (SELECT oid FROM pg_am WHERE amname = 'hash')
727 AND p1.amopclaid = p3.oid AND p1.amproc = p2.oid AND
733 -- OR NOT physically_coercible(opcintype, proargtypes[0])