3 -- Sanity checks for common errors in making operator/procedure system tables:
4 -- pg_operator, pg_proc, pg_cast, pg_aggregate, pg_am,
5 -- pg_amop, pg_amproc, pg_opclass, pg_opfamily.
7 -- None of the SELECTs here should ever find any matching entries,
8 -- so the expected output is easy to maintain ;-).
9 -- A test failure indicates someone messed up an entry in the system tables.
11 -- NB: we assume the oidjoins test will have caught any dangling links,
12 -- that is OID or REGPROC fields that are not zero and do not match some
13 -- row in the linked-to table. However, if we want to enforce that a link
14 -- field can't be 0, we have to check it here.
16 -- NB: run this test earlier than the create_operator test, because
17 -- that test creates some bogus operators...
18 -- Helper functions to deal with cases where binary-coercible matches are
20 -- This should match IsBinaryCoercible() in parse_coerce.c.
21 create function binary_coercible(oid, oid) returns bool as $$
23 EXISTS(select 1 from pg_catalog.pg_cast where
24 castsource = $1 and casttarget = $2 and
25 castmethod = 'b' and castcontext = 'i') OR
26 ($2 = 'pg_catalog.anyarray'::pg_catalog.regtype AND
27 EXISTS(select 1 from pg_catalog.pg_type where
28 oid = $1 and typelem != 0 and typlen = -1))
29 $$ language sql strict stable;
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_catalog.pg_cast where
35 castsource = $1 and casttarget = $2 and
37 ($2 = 'pg_catalog.anyarray'::pg_catalog.regtype AND
38 EXISTS(select 1 from pg_catalog.pg_type where
39 oid = $1 and typelem != 0 and typlen = -1))
40 $$ language sql strict stable;
41 -- **************** pg_proc ****************
42 -- Look for illegal values in pg_proc fields.
43 SELECT p1.oid, p1.proname
45 WHERE p1.prolang = 0 OR p1.prorettype = 0 OR
47 p1.pronargdefaults < 0 OR
48 p1.pronargdefaults > p1.pronargs OR
49 array_lower(p1.proargtypes, 1) != 0 OR
50 array_upper(p1.proargtypes, 1) != p1.pronargs-1 OR
51 0::oid = ANY (p1.proargtypes) OR
53 CASE WHEN proretset THEN prorows <= 0 ELSE prorows != 0 END;
58 -- prosrc should never be null or empty
59 SELECT p1.oid, p1.proname
61 WHERE prosrc IS NULL OR prosrc = '' OR prosrc = '-';
66 -- proiswindow shouldn't be set together with proisagg or proretset
67 SELECT p1.oid, p1.proname
69 WHERE proiswindow AND (proisagg OR proretset);
74 -- pronargdefaults should be 0 iff proargdefaults is null
75 SELECT p1.oid, p1.proname
77 WHERE (pronargdefaults <> 0) != (proargdefaults IS NOT NULL);
82 -- probin should be non-empty for C functions, null everywhere else
83 SELECT p1.oid, p1.proname
85 WHERE prolang = 13 AND (probin IS NULL OR probin = '' OR probin = '-');
90 SELECT p1.oid, p1.proname
92 WHERE prolang != 13 AND probin IS NOT NULL;
97 -- Look for conflicting proc definitions (same names and input datatypes).
98 -- (This test should be dead code now that we have the unique index
99 -- pg_proc_proname_args_nsp_index, but I'll leave it in anyway.)
100 SELECT p1.oid, p1.proname, p2.oid, p2.proname
101 FROM pg_proc AS p1, pg_proc AS p2
102 WHERE p1.oid != p2.oid AND
103 p1.proname = p2.proname AND
104 p1.pronargs = p2.pronargs AND
105 p1.proargtypes = p2.proargtypes;
106 oid | proname | oid | proname
107 -----+---------+-----+---------
110 -- Considering only built-in procs (prolang = 12), look for multiple uses
111 -- of the same internal function (ie, matching prosrc fields). It's OK to
112 -- have several entries with different pronames for the same internal function,
113 -- but conflicts in the number of arguments and other critical items should
114 -- be complained of. (We don't check data types here; see next query.)
115 -- Note: ignore aggregate functions here, since they all point to the same
116 -- dummy built-in function.
117 SELECT p1.oid, p1.proname, p2.oid, p2.proname
118 FROM pg_proc AS p1, pg_proc AS p2
119 WHERE p1.oid < p2.oid AND
120 p1.prosrc = p2.prosrc AND
121 p1.prolang = 12 AND p2.prolang = 12 AND
122 (p1.proisagg = false OR p2.proisagg = false) AND
123 (p1.prolang != p2.prolang OR
124 p1.proisagg != p2.proisagg OR
125 p1.prosecdef != p2.prosecdef OR
126 p1.proisstrict != p2.proisstrict OR
127 p1.proretset != p2.proretset OR
128 p1.provolatile != p2.provolatile OR
129 p1.pronargs != p2.pronargs);
130 oid | proname | oid | proname
131 -----+---------+-----+---------
134 -- Look for uses of different type OIDs in the argument/result type fields
135 -- for different aliases of the same built-in function.
136 -- This indicates that the types are being presumed to be binary-equivalent,
137 -- or that the built-in function is prepared to deal with different types.
138 -- That's not wrong, necessarily, but we make lists of all the types being
139 -- so treated. Note that the expected output of this part of the test will
140 -- need to be modified whenever new pairs of types are made binary-equivalent,
141 -- or when new polymorphic built-in functions are added!
142 -- Note: ignore aggregate functions here, since they all point to the same
143 -- dummy built-in function.
144 SELECT DISTINCT p1.prorettype, p2.prorettype
145 FROM pg_proc AS p1, pg_proc AS p2
146 WHERE p1.oid != p2.oid AND
147 p1.prosrc = p2.prosrc AND
148 p1.prolang = 12 AND p2.prolang = 12 AND
149 NOT p1.proisagg AND NOT p2.proisagg AND
150 (p1.prorettype < p2.prorettype)
152 prorettype | prorettype
153 ------------+------------
158 SELECT DISTINCT p1.proargtypes[0], p2.proargtypes[0]
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[0] < p2.proargtypes[0])
166 proargtypes | proargtypes
167 -------------+-------------
175 SELECT DISTINCT p1.proargtypes[1], p2.proargtypes[1]
176 FROM pg_proc AS p1, pg_proc AS p2
177 WHERE p1.oid != p2.oid AND
178 p1.prosrc = p2.prosrc AND
179 p1.prolang = 12 AND p2.prolang = 12 AND
180 NOT p1.proisagg AND NOT p2.proisagg AND
181 (p1.proargtypes[1] < p2.proargtypes[1])
183 proargtypes | proargtypes
184 -------------+-------------
191 SELECT DISTINCT p1.proargtypes[2], p2.proargtypes[2]
192 FROM pg_proc AS p1, pg_proc AS p2
193 WHERE p1.oid != p2.oid AND
194 p1.prosrc = p2.prosrc AND
195 p1.prolang = 12 AND p2.prolang = 12 AND
196 NOT p1.proisagg AND NOT p2.proisagg AND
197 (p1.proargtypes[2] < p2.proargtypes[2])
199 proargtypes | proargtypes
200 -------------+-------------
204 SELECT DISTINCT p1.proargtypes[3], p2.proargtypes[3]
205 FROM pg_proc AS p1, pg_proc AS p2
206 WHERE p1.oid != p2.oid AND
207 p1.prosrc = p2.prosrc AND
208 p1.prolang = 12 AND p2.prolang = 12 AND
209 NOT p1.proisagg AND NOT p2.proisagg AND
210 (p1.proargtypes[3] < p2.proargtypes[3])
212 proargtypes | proargtypes
213 -------------+-------------
217 SELECT DISTINCT p1.proargtypes[4], p2.proargtypes[4]
218 FROM pg_proc AS p1, pg_proc AS p2
219 WHERE p1.oid != p2.oid AND
220 p1.prosrc = p2.prosrc AND
221 p1.prolang = 12 AND p2.prolang = 12 AND
222 NOT p1.proisagg AND NOT p2.proisagg AND
223 (p1.proargtypes[4] < p2.proargtypes[4])
225 proargtypes | proargtypes
226 -------------+-------------
229 SELECT DISTINCT p1.proargtypes[5], p2.proargtypes[5]
230 FROM pg_proc AS p1, pg_proc AS p2
231 WHERE p1.oid != p2.oid AND
232 p1.prosrc = p2.prosrc AND
233 p1.prolang = 12 AND p2.prolang = 12 AND
234 NOT p1.proisagg AND NOT p2.proisagg AND
235 (p1.proargtypes[5] < p2.proargtypes[5])
237 proargtypes | proargtypes
238 -------------+-------------
241 SELECT DISTINCT p1.proargtypes[6], p2.proargtypes[6]
242 FROM pg_proc AS p1, pg_proc AS p2
243 WHERE p1.oid != p2.oid AND
244 p1.prosrc = p2.prosrc AND
245 p1.prolang = 12 AND p2.prolang = 12 AND
246 NOT p1.proisagg AND NOT p2.proisagg AND
247 (p1.proargtypes[6] < p2.proargtypes[6])
249 proargtypes | proargtypes
250 -------------+-------------
253 SELECT DISTINCT p1.proargtypes[7], p2.proargtypes[7]
254 FROM pg_proc AS p1, pg_proc AS p2
255 WHERE p1.oid != p2.oid AND
256 p1.prosrc = p2.prosrc AND
257 p1.prolang = 12 AND p2.prolang = 12 AND
258 NOT p1.proisagg AND NOT p2.proisagg AND
259 (p1.proargtypes[7] < p2.proargtypes[7])
261 proargtypes | proargtypes
262 -------------+-------------
265 -- Look for functions that return type "internal" and do not have any
266 -- "internal" argument. Such a function would be a security hole since
267 -- it might be used to call an internal function from an SQL command.
268 -- As of 7.3 this query should find only internal_in.
269 SELECT p1.oid, p1.proname
271 WHERE p1.prorettype = 'internal'::regtype AND NOT
272 'internal'::regtype = ANY (p1.proargtypes);
278 -- Check for length inconsistencies between the various argument-info arrays.
279 SELECT p1.oid, p1.proname
281 WHERE proallargtypes IS NOT NULL AND
282 array_length(proallargtypes,1) < array_length(proargtypes,1);
287 SELECT p1.oid, p1.proname
289 WHERE proargmodes IS NOT NULL AND
290 array_length(proargmodes,1) < array_length(proargtypes,1);
295 SELECT p1.oid, p1.proname
297 WHERE proargnames IS NOT NULL AND
298 array_length(proargnames,1) < array_length(proargtypes,1);
303 SELECT p1.oid, p1.proname
305 WHERE proallargtypes IS NOT NULL AND proargmodes IS NOT NULL AND
306 array_length(proallargtypes,1) <> array_length(proargmodes,1);
311 SELECT p1.oid, p1.proname
313 WHERE proallargtypes IS NOT NULL AND proargnames IS NOT NULL AND
314 array_length(proallargtypes,1) <> array_length(proargnames,1);
319 SELECT p1.oid, p1.proname
321 WHERE proargmodes IS NOT NULL AND proargnames IS NOT NULL AND
322 array_length(proargmodes,1) <> array_length(proargnames,1);
327 -- **************** pg_cast ****************
328 -- Catch bogus values in pg_cast columns (other than cases detected by
332 WHERE castsource = 0 OR casttarget = 0 OR castcontext NOT IN ('e', 'a', 'i')
333 OR castmethod NOT IN ('f', 'b' ,'i');
334 castsource | casttarget | castfunc | castcontext | castmethod
335 ------------+------------+----------+-------------+------------
338 -- Check that castfunc is nonzero only for cast methods that need a function,
339 -- and zero otherwise
342 WHERE (castmethod = 'f' AND castfunc = 0)
343 OR (castmethod IN ('b', 'i') AND castfunc <> 0);
344 castsource | casttarget | castfunc | castcontext | castmethod
345 ------------+------------+----------+-------------+------------
348 -- Look for casts to/from the same type that aren't length coercion functions.
349 -- (We assume they are length coercions if they take multiple arguments.)
350 -- Such entries are not necessarily harmful, but they are useless.
353 WHERE castsource = casttarget AND castfunc = 0;
354 castsource | casttarget | castfunc | castcontext | castmethod
355 ------------+------------+----------+-------------+------------
359 FROM pg_cast c, pg_proc p
360 WHERE c.castfunc = p.oid AND p.pronargs < 2 AND castsource = casttarget;
361 castsource | casttarget | castfunc | castcontext | castmethod
362 ------------+------------+----------+-------------+------------
365 -- Look for cast functions that don't have the right signature. The
366 -- argument and result types in pg_proc must be the same as, or binary
367 -- compatible with, what it says in pg_cast.
368 -- As a special case, we allow casts from CHAR(n) that use functions
369 -- declared to take TEXT. This does not pass the binary-coercibility test
370 -- because CHAR(n)-to-TEXT normally invokes rtrim(). However, the results
371 -- are the same, so long as the function is one that ignores trailing blanks.
373 FROM pg_cast c, pg_proc p
374 WHERE c.castfunc = p.oid AND
375 (p.pronargs < 1 OR p.pronargs > 3
376 OR NOT (binary_coercible(c.castsource, p.proargtypes[0])
377 OR (c.castsource = 'character'::regtype AND
378 p.proargtypes[0] = 'text'::regtype))
379 OR NOT binary_coercible(p.prorettype, c.casttarget));
380 castsource | casttarget | castfunc | castcontext | castmethod
381 ------------+------------+----------+-------------+------------
385 FROM pg_cast c, pg_proc p
386 WHERE c.castfunc = p.oid AND
387 ((p.pronargs > 1 AND p.proargtypes[1] != 'int4'::regtype) OR
388 (p.pronargs > 2 AND p.proargtypes[2] != 'bool'::regtype));
389 castsource | casttarget | castfunc | castcontext | castmethod
390 ------------+------------+----------+-------------+------------
393 -- Look for binary compatible casts that do not have the reverse
394 -- direction registered as well, or where the reverse direction is not
395 -- also binary compatible. This is legal, but usually not intended.
396 -- As of 7.4, this finds the casts from text and varchar to bpchar, because
397 -- those are binary-compatible while the reverse way goes through rtrim().
398 -- As of 8.2, this finds the cast from cidr to inet, because that is a
399 -- trivial binary coercion while the other way goes through inet_to_cidr().
400 -- As of 8.3, this finds the casts from xml to text, varchar, and bpchar,
401 -- because those are binary-compatible while the reverse goes through
402 -- texttoxml(), which does an XML syntax check.
403 -- As of 9.1, this finds the cast from pg_node_tree to text, which we
404 -- intentionally do not provide a reverse pathway for.
405 SELECT castsource::regtype, casttarget::regtype, castfunc, castcontext
407 WHERE c.castmethod = 'b' AND
408 NOT EXISTS (SELECT 1 FROM pg_cast k
409 WHERE k.castmethod = 'b' AND
410 k.castsource = c.casttarget AND
411 k.casttarget = c.castsource);
412 castsource | casttarget | castfunc | castcontext
413 -------------------+-------------------+----------+-------------
414 text | character | 0 | i
415 character varying | character | 0 | i
416 pg_node_tree | text | 0 | i
419 xml | character varying | 0 | a
420 xml | character | 0 | a
423 -- **************** pg_operator ****************
424 -- Look for illegal values in pg_operator fields.
425 SELECT p1.oid, p1.oprname
426 FROM pg_operator as p1
427 WHERE (p1.oprkind != 'b' AND p1.oprkind != 'l' AND p1.oprkind != 'r') OR
428 p1.oprresult = 0 OR p1.oprcode = 0;
433 -- Look for missing or unwanted operand types
434 SELECT p1.oid, p1.oprname
435 FROM pg_operator as p1
436 WHERE (p1.oprleft = 0 and p1.oprkind != 'l') OR
437 (p1.oprleft != 0 and p1.oprkind = 'l') OR
438 (p1.oprright = 0 and p1.oprkind != 'r') OR
439 (p1.oprright != 0 and p1.oprkind = 'r');
444 -- Look for conflicting operator definitions (same names and input datatypes).
445 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
446 FROM pg_operator AS p1, pg_operator AS p2
447 WHERE p1.oid != p2.oid AND
448 p1.oprname = p2.oprname AND
449 p1.oprkind = p2.oprkind AND
450 p1.oprleft = p2.oprleft AND
451 p1.oprright = p2.oprright;
452 oid | oprcode | oid | oprcode
453 -----+---------+-----+---------
456 -- Look for commutative operators that don't commute.
457 -- DEFINITIONAL NOTE: If A.oprcom = B, then x A y has the same result as y B x.
458 -- We expect that B will always say that B.oprcom = A as well; that's not
459 -- inherently essential, but it would be inefficient not to mark it so.
460 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
461 FROM pg_operator AS p1, pg_operator AS p2
462 WHERE p1.oprcom = p2.oid AND
463 (p1.oprkind != 'b' OR
464 p1.oprleft != p2.oprright OR
465 p1.oprright != p2.oprleft OR
466 p1.oprresult != p2.oprresult OR
467 p1.oid != p2.oprcom);
468 oid | oprcode | oid | oprcode
469 -----+---------+-----+---------
472 -- Look for negatory operators that don't agree.
473 -- DEFINITIONAL NOTE: If A.oprnegate = B, then both A and B must yield
474 -- boolean results, and (x A y) == ! (x B y), or the equivalent for
475 -- single-operand operators.
476 -- We expect that B will always say that B.oprnegate = A as well; that's not
477 -- inherently essential, but it would be inefficient not to mark it so.
478 -- Also, A and B had better not be the same operator.
479 SELECT p1.oid, p1.oprcode, p2.oid, p2.oprcode
480 FROM pg_operator AS p1, pg_operator AS p2
481 WHERE p1.oprnegate = p2.oid AND
482 (p1.oprkind != p2.oprkind OR
483 p1.oprleft != p2.oprleft OR
484 p1.oprright != p2.oprright OR
485 p1.oprresult != 'bool'::regtype OR
486 p2.oprresult != 'bool'::regtype OR
487 p1.oid != p2.oprnegate OR
489 oid | oprcode | oid | oprcode
490 -----+---------+-----+---------
493 -- A mergejoinable or hashjoinable operator must be binary, must return
494 -- boolean, and must have a commutator (itself, unless it's a cross-type
496 SELECT p1.oid, p1.oprname FROM pg_operator AS p1
497 WHERE (p1.oprcanmerge OR p1.oprcanhash) AND NOT
498 (p1.oprkind = 'b' AND p1.oprresult = 'bool'::regtype AND p1.oprcom != 0);
503 -- What's more, the commutator had better be mergejoinable/hashjoinable too.
504 SELECT p1.oid, p1.oprname, p2.oid, p2.oprname
505 FROM pg_operator AS p1, pg_operator AS p2
506 WHERE p1.oprcom = p2.oid AND
507 (p1.oprcanmerge != p2.oprcanmerge OR
508 p1.oprcanhash != p2.oprcanhash);
509 oid | oprname | oid | oprname
510 -----+---------+-----+---------
513 -- Mergejoinable operators should appear as equality members of btree index
515 SELECT p1.oid, p1.oprname
516 FROM pg_operator AS p1
517 WHERE p1.oprcanmerge AND NOT EXISTS
518 (SELECT 1 FROM pg_amop
519 WHERE amopmethod = (SELECT oid FROM pg_am WHERE amname = 'btree') AND
520 amopopr = p1.oid AND amopstrategy = 3);
526 SELECT p1.oid, p1.oprname, p.amopfamily
527 FROM pg_operator AS p1, pg_amop p
528 WHERE amopopr = p1.oid
529 AND amopmethod = (SELECT oid FROM pg_am WHERE amname = 'btree')
531 AND NOT p1.oprcanmerge;
532 oid | oprname | amopfamily
533 -----+---------+------------
536 -- Hashable operators should appear as members of hash index opfamilies.
537 SELECT p1.oid, p1.oprname
538 FROM pg_operator AS p1
539 WHERE p1.oprcanhash AND NOT EXISTS
540 (SELECT 1 FROM pg_amop
541 WHERE amopmethod = (SELECT oid FROM pg_am WHERE amname = 'hash') AND
542 amopopr = p1.oid AND amopstrategy = 1);
548 SELECT p1.oid, p1.oprname, p.amopfamily
549 FROM pg_operator AS p1, pg_amop p
550 WHERE amopopr = p1.oid
551 AND amopmethod = (SELECT oid FROM pg_am WHERE amname = 'hash')
552 AND NOT p1.oprcanhash;
553 oid | oprname | amopfamily
554 -----+---------+------------
557 -- Check that each operator defined in pg_operator matches its oprcode entry
558 -- in pg_proc. Easiest to do this separately for each oprkind.
559 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
560 FROM pg_operator AS p1, pg_proc AS p2
561 WHERE p1.oprcode = p2.oid AND
564 OR NOT binary_coercible(p2.prorettype, p1.oprresult)
565 OR NOT binary_coercible(p1.oprleft, p2.proargtypes[0])
566 OR NOT binary_coercible(p1.oprright, p2.proargtypes[1]));
567 oid | oprname | oid | proname
568 -----+---------+-----+---------
571 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
572 FROM pg_operator AS p1, pg_proc AS p2
573 WHERE p1.oprcode = p2.oid AND
576 OR NOT binary_coercible(p2.prorettype, p1.oprresult)
577 OR NOT binary_coercible(p1.oprright, p2.proargtypes[0])
579 oid | oprname | oid | proname
580 -----+---------+-----+---------
583 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
584 FROM pg_operator AS p1, pg_proc AS p2
585 WHERE p1.oprcode = p2.oid AND
588 OR NOT binary_coercible(p2.prorettype, p1.oprresult)
589 OR NOT binary_coercible(p1.oprleft, p2.proargtypes[0])
590 OR p1.oprright != 0);
591 oid | oprname | oid | proname
592 -----+---------+-----+---------
595 -- If the operator is mergejoinable or hashjoinable, its underlying function
596 -- should not be volatile.
597 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
598 FROM pg_operator AS p1, pg_proc AS p2
599 WHERE p1.oprcode = p2.oid AND
600 (p1.oprcanmerge OR p1.oprcanhash) AND
601 p2.provolatile = 'v';
602 oid | oprname | oid | proname
603 -----+---------+-----+---------
606 -- If oprrest is set, the operator must return boolean,
607 -- and it must link to a proc with the right signature
608 -- to be a restriction selectivity estimator.
609 -- The proc signature we want is: float8 proc(internal, oid, internal, int4)
610 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
611 FROM pg_operator AS p1, pg_proc AS p2
612 WHERE p1.oprrest = p2.oid AND
613 (p1.oprresult != 'bool'::regtype OR
614 p2.prorettype != 'float8'::regtype OR p2.proretset OR
616 p2.proargtypes[0] != 'internal'::regtype OR
617 p2.proargtypes[1] != 'oid'::regtype OR
618 p2.proargtypes[2] != 'internal'::regtype OR
619 p2.proargtypes[3] != 'int4'::regtype);
620 oid | oprname | oid | proname
621 -----+---------+-----+---------
624 -- If oprjoin is set, the operator must be a binary boolean op,
625 -- and it must link to a proc with the right signature
626 -- to be a join selectivity estimator.
627 -- The proc signature we want is: float8 proc(internal, oid, internal, int2, internal)
628 -- (Note: the old signature with only 4 args is still allowed, but no core
629 -- estimator should be using it.)
630 SELECT p1.oid, p1.oprname, p2.oid, p2.proname
631 FROM pg_operator AS p1, pg_proc AS p2
632 WHERE p1.oprjoin = p2.oid AND
633 (p1.oprkind != 'b' OR p1.oprresult != 'bool'::regtype OR
634 p2.prorettype != 'float8'::regtype OR p2.proretset OR
636 p2.proargtypes[0] != 'internal'::regtype OR
637 p2.proargtypes[1] != 'oid'::regtype OR
638 p2.proargtypes[2] != 'internal'::regtype OR
639 p2.proargtypes[3] != 'int2'::regtype OR
640 p2.proargtypes[4] != 'internal'::regtype);
641 oid | oprname | oid | proname
642 -----+---------+-----+---------
645 -- **************** pg_aggregate ****************
646 -- Look for illegal values in pg_aggregate fields.
647 SELECT ctid, aggfnoid::oid
648 FROM pg_aggregate as p1
649 WHERE aggfnoid = 0 OR aggtransfn = 0 OR aggtranstype = 0;
654 -- Make sure the matching pg_proc entry is sensible, too.
655 SELECT a.aggfnoid::oid, p.proname
656 FROM pg_aggregate as a, pg_proc as p
657 WHERE a.aggfnoid = p.oid AND
658 (NOT p.proisagg OR p.proretset);
663 -- Make sure there are no proisagg pg_proc entries without matches.
667 NOT EXISTS (SELECT 1 FROM pg_aggregate a WHERE a.aggfnoid = p.oid);
672 -- If there is no finalfn then the output type must be the transtype.
673 SELECT a.aggfnoid::oid, p.proname
674 FROM pg_aggregate as a, pg_proc as p
675 WHERE a.aggfnoid = p.oid AND
676 a.aggfinalfn = 0 AND p.prorettype != a.aggtranstype;
681 -- Cross-check transfn against its entry in pg_proc.
682 -- NOTE: use physically_coercible here, not binary_coercible, because
683 -- max and min on abstime are implemented using int4larger/int4smaller.
684 SELECT a.aggfnoid::oid, p.proname, ptr.oid, ptr.proname
685 FROM pg_aggregate AS a, pg_proc AS p, pg_proc AS ptr
686 WHERE a.aggfnoid = p.oid AND
687 a.aggtransfn = ptr.oid AND
689 OR NOT (ptr.pronargs = p.pronargs + 1)
690 OR NOT physically_coercible(ptr.prorettype, a.aggtranstype)
691 OR NOT physically_coercible(a.aggtranstype, ptr.proargtypes[0])
692 OR (p.pronargs > 0 AND
693 NOT physically_coercible(p.proargtypes[0], ptr.proargtypes[1]))
694 OR (p.pronargs > 1 AND
695 NOT physically_coercible(p.proargtypes[1], ptr.proargtypes[2]))
696 OR (p.pronargs > 2 AND
697 NOT physically_coercible(p.proargtypes[2], ptr.proargtypes[3]))
698 -- we could carry the check further, but that's enough for now
700 aggfnoid | proname | oid | proname
701 ----------+---------+-----+---------
704 -- Cross-check finalfn (if present) against its entry in pg_proc.
705 SELECT a.aggfnoid::oid, p.proname, pfn.oid, pfn.proname
706 FROM pg_aggregate AS a, pg_proc AS p, pg_proc AS pfn
707 WHERE a.aggfnoid = p.oid AND
708 a.aggfinalfn = pfn.oid AND
710 OR NOT binary_coercible(pfn.prorettype, p.prorettype)
712 OR NOT binary_coercible(a.aggtranstype, pfn.proargtypes[0]));
713 aggfnoid | proname | oid | proname
714 ----------+---------+-----+---------
717 -- If transfn is strict then either initval should be non-NULL, or
718 -- input type should match transtype so that the first non-null input
719 -- can be assigned as the state value.
720 SELECT a.aggfnoid::oid, p.proname, ptr.oid, ptr.proname
721 FROM pg_aggregate AS a, pg_proc AS p, pg_proc AS ptr
722 WHERE a.aggfnoid = p.oid AND
723 a.aggtransfn = ptr.oid AND ptr.proisstrict AND
724 a.agginitval IS NULL AND
725 NOT binary_coercible(p.proargtypes[0], a.aggtranstype);
726 aggfnoid | proname | oid | proname
727 ----------+---------+-----+---------
730 -- Cross-check aggsortop (if present) against pg_operator.
731 -- We expect to find only "<" for "min" and ">" for "max".
732 SELECT DISTINCT proname, oprname
733 FROM pg_operator AS o, pg_aggregate AS a, pg_proc AS p
734 WHERE a.aggfnoid = p.oid AND a.aggsortop = o.oid
742 -- Check datatypes match
743 SELECT a.aggfnoid::oid, o.oid
744 FROM pg_operator AS o, pg_aggregate AS a, pg_proc AS p
745 WHERE a.aggfnoid = p.oid AND a.aggsortop = o.oid AND
746 (oprkind != 'b' OR oprresult != 'boolean'::regtype
747 OR oprleft != p.proargtypes[0] OR oprright != p.proargtypes[0]);
752 -- Check operator is a suitable btree opfamily member
753 SELECT a.aggfnoid::oid, o.oid
754 FROM pg_operator AS o, pg_aggregate AS a, pg_proc AS p
755 WHERE a.aggfnoid = p.oid AND a.aggsortop = o.oid AND
756 NOT EXISTS(SELECT 1 FROM pg_amop
757 WHERE amopmethod = (SELECT oid FROM pg_am WHERE amname = 'btree')
759 AND amoplefttype = o.oprleft
760 AND amoprighttype = o.oprright);
765 -- Check correspondence of btree strategies and names
766 SELECT DISTINCT proname, oprname, amopstrategy
767 FROM pg_operator AS o, pg_aggregate AS a, pg_proc AS p,
769 WHERE a.aggfnoid = p.oid AND a.aggsortop = o.oid AND
771 amopmethod = (SELECT oid FROM pg_am WHERE amname = 'btree')
773 proname | oprname | amopstrategy
774 ---------+---------+--------------
779 -- Check that there are not aggregates with the same name and different
780 -- numbers of arguments. While not technically wrong, we have a project policy
781 -- to avoid this because it opens the door for confusion in connection with
782 -- ORDER BY: novices frequently put the ORDER BY in the wrong place.
783 -- See the fate of the single-argument form of string_agg() for history.
784 -- The only aggregates that should show up here are count(x) and count(*).
785 SELECT p1.oid::regprocedure, p2.oid::regprocedure
786 FROM pg_proc AS p1, pg_proc AS p2
787 WHERE p1.oid < p2.oid AND p1.proname = p2.proname AND
788 p1.proisagg AND p2.proisagg AND
789 array_dims(p1.proargtypes) != array_dims(p2.proargtypes)
792 --------------+---------
793 count("any") | count()
796 -- For the same reason, aggregates with default arguments are no good.
799 WHERE proisagg AND proargdefaults IS NOT NULL;
804 -- **************** pg_opfamily ****************
805 -- Look for illegal values in pg_opfamily fields
807 FROM pg_opfamily as p1
808 WHERE p1.opfmethod = 0 OR p1.opfnamespace = 0;
813 -- **************** pg_opclass ****************
814 -- Look for illegal values in pg_opclass fields
816 FROM pg_opclass AS p1
817 WHERE p1.opcmethod = 0 OR p1.opcnamespace = 0 OR p1.opcfamily = 0
823 -- opcmethod must match owning opfamily's opfmethod
824 SELECT p1.oid, p2.oid
825 FROM pg_opclass AS p1, pg_opfamily AS p2
826 WHERE p1.opcfamily = p2.oid AND p1.opcmethod != p2.opfmethod;
831 -- There should not be multiple entries in pg_opclass with opcdefault true
832 -- and the same opcmethod/opcintype combination.
833 SELECT p1.oid, p2.oid
834 FROM pg_opclass AS p1, pg_opclass AS p2
835 WHERE p1.oid != p2.oid AND
836 p1.opcmethod = p2.opcmethod AND p1.opcintype = p2.opcintype AND
837 p1.opcdefault AND p2.opcdefault;
842 -- **************** pg_amop ****************
843 -- Look for illegal values in pg_amop fields
844 SELECT p1.amopfamily, p1.amopstrategy
846 WHERE p1.amopfamily = 0 OR p1.amoplefttype = 0 OR p1.amoprighttype = 0
847 OR p1.amopopr = 0 OR p1.amopmethod = 0 OR p1.amopstrategy < 1;
848 amopfamily | amopstrategy
849 ------------+--------------
852 SELECT p1.amopfamily, p1.amopstrategy
854 WHERE NOT ((p1.amoppurpose = 's' AND p1.amopsortfamily = 0) OR
855 (p1.amoppurpose = 'o' AND p1.amopsortfamily <> 0));
856 amopfamily | amopstrategy
857 ------------+--------------
860 -- amoplefttype/amoprighttype must match the operator
861 SELECT p1.oid, p2.oid
862 FROM pg_amop AS p1, pg_operator AS p2
863 WHERE p1.amopopr = p2.oid AND NOT
864 (p1.amoplefttype = p2.oprleft AND p1.amoprighttype = p2.oprright);
869 -- amopmethod must match owning opfamily's opfmethod
870 SELECT p1.oid, p2.oid
871 FROM pg_amop AS p1, pg_opfamily AS p2
872 WHERE p1.amopfamily = p2.oid AND p1.amopmethod != p2.opfmethod;
877 -- amopsortfamily, if present, must reference a btree family
878 SELECT p1.amopfamily, p1.amopstrategy
880 WHERE p1.amopsortfamily <> 0 AND NOT EXISTS
881 (SELECT 1 from pg_opfamily op WHERE op.oid = p1.amopsortfamily
882 AND op.opfmethod = (SELECT oid FROM pg_am WHERE amname = 'btree'));
883 amopfamily | amopstrategy
884 ------------+--------------
887 -- check for ordering operators not supported by parent AM
888 SELECT p1.amopfamily, p1.amopopr, p2.oid, p2.amname
889 FROM pg_amop AS p1, pg_am AS p2
890 WHERE p1.amopmethod = p2.oid AND
891 p1.amoppurpose = 'o' AND NOT p2.amcanorderbyop;
892 amopfamily | amopopr | oid | amname
893 ------------+---------+-----+--------
896 -- Cross-check amopstrategy index against parent AM
897 SELECT p1.amopfamily, p1.amopopr, p2.oid, p2.amname
898 FROM pg_amop AS p1, pg_am AS p2
899 WHERE p1.amopmethod = p2.oid AND
900 p1.amopstrategy > p2.amstrategies AND p2.amstrategies <> 0;
901 amopfamily | amopopr | oid | amname
902 ------------+---------+-----+--------
905 -- Detect missing pg_amop entries: should have as many strategy operators
906 -- as AM expects for each datatype combination supported by the opfamily.
907 -- We can't check this for AMs with variable strategy sets.
908 SELECT p1.amname, p2.amoplefttype, p2.amoprighttype
909 FROM pg_am AS p1, pg_amop AS p2
910 WHERE p2.amopmethod = p1.oid AND
911 p1.amstrategies <> 0 AND
912 p1.amstrategies != (SELECT count(*) FROM pg_amop AS p3
913 WHERE p3.amopfamily = p2.amopfamily AND
914 p3.amoplefttype = p2.amoplefttype AND
915 p3.amoprighttype = p2.amoprighttype AND
916 p3.amoppurpose = 's');
917 amname | amoplefttype | amoprighttype
918 --------+--------------+---------------
921 -- Currently, none of the AMs with fixed strategy sets support ordering ops.
922 SELECT p1.amname, p2.amopfamily, p2.amopstrategy
923 FROM pg_am AS p1, pg_amop AS p2
924 WHERE p2.amopmethod = p1.oid AND
925 p1.amstrategies <> 0 AND p2.amoppurpose <> 's';
926 amname | amopfamily | amopstrategy
927 --------+------------+--------------
930 -- Check that amopopr points at a reasonable-looking operator, ie a binary
931 -- operator. If it's a search operator it had better yield boolean,
932 -- otherwise an input type of its sort opfamily.
933 SELECT p1.amopfamily, p1.amopopr, p2.oid, p2.oprname
934 FROM pg_amop AS p1, pg_operator AS p2
935 WHERE p1.amopopr = p2.oid AND
937 amopfamily | amopopr | oid | oprname
938 ------------+---------+-----+---------
941 SELECT p1.amopfamily, p1.amopopr, p2.oid, p2.oprname
942 FROM pg_amop AS p1, pg_operator AS p2
943 WHERE p1.amopopr = p2.oid AND p1.amoppurpose = 's' AND
944 p2.oprresult != 'bool'::regtype;
945 amopfamily | amopopr | oid | oprname
946 ------------+---------+-----+---------
949 SELECT p1.amopfamily, p1.amopopr, p2.oid, p2.oprname
950 FROM pg_amop AS p1, pg_operator AS p2
951 WHERE p1.amopopr = p2.oid AND p1.amoppurpose = 'o' AND NOT EXISTS
952 (SELECT 1 FROM pg_opclass op
953 WHERE opcfamily = p1.amopsortfamily AND opcintype = p2.oprresult);
954 amopfamily | amopopr | oid | oprname
955 ------------+---------+-----+---------
958 -- Make a list of all the distinct operator names being used in particular
959 -- strategy slots. This is a bit hokey, since the list might need to change
960 -- in future releases, but it's an effective way of spotting mistakes such as
961 -- swapping two operators within a family.
962 SELECT DISTINCT amopmethod, amopstrategy, oprname
963 FROM pg_amop p1 LEFT JOIN pg_operator p2 ON amopopr = p2.oid
965 amopmethod | amopstrategy | oprname
966 ------------+--------------+---------
1008 -- Check that all opclass search operators have selectivity estimators.
1009 -- This is not absolutely required, but it seems a reasonable thing
1010 -- to insist on for all standard datatypes.
1011 SELECT p1.amopfamily, p1.amopopr, p2.oid, p2.oprname
1012 FROM pg_amop AS p1, pg_operator AS p2
1013 WHERE p1.amopopr = p2.oid AND p1.amoppurpose = 's' AND
1014 (p2.oprrest = 0 OR p2.oprjoin = 0);
1015 amopfamily | amopopr | oid | oprname
1016 ------------+---------+-----+---------
1019 -- Check that each opclass in an opfamily has associated operators, that is
1020 -- ones whose oprleft matches opcintype (possibly by coercion).
1021 SELECT p1.opcname, p1.opcfamily
1022 FROM pg_opclass AS p1
1023 WHERE NOT EXISTS(SELECT 1 FROM pg_amop AS p2
1024 WHERE p2.amopfamily = p1.opcfamily
1025 AND binary_coercible(p1.opcintype, p2.amoplefttype));
1027 ---------+-----------
1030 -- Operators that are primary members of opclasses must be immutable (else
1031 -- it suggests that the index ordering isn't fixed). Operators that are
1032 -- cross-type members need only be stable, since they are just shorthands
1033 -- for index probe queries.
1034 SELECT p1.amopfamily, p1.amopopr, p2.oprname, p3.prosrc
1035 FROM pg_amop AS p1, pg_operator AS p2, pg_proc AS p3
1036 WHERE p1.amopopr = p2.oid AND p2.oprcode = p3.oid AND
1037 p1.amoplefttype = p1.amoprighttype AND
1038 p3.provolatile != 'i';
1039 amopfamily | amopopr | oprname | prosrc
1040 ------------+---------+---------+--------
1043 SELECT p1.amopfamily, p1.amopopr, p2.oprname, p3.prosrc
1044 FROM pg_amop AS p1, pg_operator AS p2, pg_proc AS p3
1045 WHERE p1.amopopr = p2.oid AND p2.oprcode = p3.oid AND
1046 p1.amoplefttype != p1.amoprighttype AND
1047 p3.provolatile = 'v';
1048 amopfamily | amopopr | oprname | prosrc
1049 ------------+---------+---------+--------
1052 -- Multiple-datatype btree opfamilies should provide closed sets of equality
1053 -- operators; that is if you provide int2 = int4 and int4 = int8 then you
1054 -- should also provide int2 = int8 (and commutators of all these). This is
1055 -- important because the planner tries to deduce additional qual clauses from
1056 -- transitivity of mergejoinable operators. If there are clauses
1057 -- int2var = int4var and int4var = int8var, the planner will want to deduce
1058 -- int2var = int8var ... so there should be a way to represent that. While
1059 -- a missing cross-type operator is now only an efficiency loss rather than
1060 -- an error condition, it still seems reasonable to insist that all built-in
1061 -- opfamilies be complete.
1062 -- check commutative closure
1063 SELECT p1.amoplefttype, p1.amoprighttype
1065 WHERE p1.amopmethod = (SELECT oid FROM pg_am WHERE amname = 'btree') AND
1066 p1.amopstrategy = 3 AND
1067 p1.amoplefttype != p1.amoprighttype AND
1068 NOT EXISTS(SELECT 1 FROM pg_amop p2 WHERE
1069 p2.amopfamily = p1.amopfamily AND
1070 p2.amoplefttype = p1.amoprighttype AND
1071 p2.amoprighttype = p1.amoplefttype AND
1072 p2.amopstrategy = 3);
1073 amoplefttype | amoprighttype
1074 --------------+---------------
1077 -- check transitive closure
1078 SELECT p1.amoplefttype, p1.amoprighttype, p2.amoprighttype
1079 FROM pg_amop AS p1, pg_amop AS p2
1080 WHERE p1.amopfamily = p2.amopfamily AND
1081 p1.amoprighttype = p2.amoplefttype AND
1082 p1.amopmethod = (SELECT oid FROM pg_am WHERE amname = 'btree') AND
1083 p2.amopmethod = (SELECT oid FROM pg_am WHERE amname = 'btree') AND
1084 p1.amopstrategy = 3 AND p2.amopstrategy = 3 AND
1085 p1.amoplefttype != p1.amoprighttype AND
1086 p2.amoplefttype != p2.amoprighttype AND
1087 NOT EXISTS(SELECT 1 FROM pg_amop p3 WHERE
1088 p3.amopfamily = p1.amopfamily AND
1089 p3.amoplefttype = p1.amoplefttype AND
1090 p3.amoprighttype = p2.amoprighttype AND
1091 p3.amopstrategy = 3);
1092 amoplefttype | amoprighttype | amoprighttype
1093 --------------+---------------+---------------
1096 -- We also expect that built-in multiple-datatype hash opfamilies provide
1097 -- complete sets of cross-type operators. Again, this isn't required, but
1098 -- it is reasonable to expect it for built-in opfamilies.
1099 -- if same family has x=x and y=y, it should have x=y
1100 SELECT p1.amoplefttype, p2.amoplefttype
1101 FROM pg_amop AS p1, pg_amop AS p2
1102 WHERE p1.amopfamily = p2.amopfamily AND
1103 p1.amoplefttype = p1.amoprighttype AND
1104 p2.amoplefttype = p2.amoprighttype AND
1105 p1.amopmethod = (SELECT oid FROM pg_am WHERE amname = 'hash') AND
1106 p2.amopmethod = (SELECT oid FROM pg_am WHERE amname = 'hash') AND
1107 p1.amopstrategy = 1 AND p2.amopstrategy = 1 AND
1108 p1.amoplefttype != p2.amoplefttype AND
1109 NOT EXISTS(SELECT 1 FROM pg_amop p3 WHERE
1110 p3.amopfamily = p1.amopfamily AND
1111 p3.amoplefttype = p1.amoplefttype AND
1112 p3.amoprighttype = p2.amoplefttype AND
1113 p3.amopstrategy = 1);
1114 amoplefttype | amoplefttype
1115 --------------+--------------
1118 -- **************** pg_amproc ****************
1119 -- Look for illegal values in pg_amproc fields
1120 SELECT p1.amprocfamily, p1.amprocnum
1121 FROM pg_amproc as p1
1122 WHERE p1.amprocfamily = 0 OR p1.amproclefttype = 0 OR p1.amprocrighttype = 0
1123 OR p1.amprocnum < 1 OR p1.amproc = 0;
1124 amprocfamily | amprocnum
1125 --------------+-----------
1128 -- Cross-check amprocnum index against parent AM
1129 SELECT p1.amprocfamily, p1.amprocnum, p2.oid, p2.amname
1130 FROM pg_amproc AS p1, pg_am AS p2, pg_opfamily AS p3
1131 WHERE p1.amprocfamily = p3.oid AND p3.opfmethod = p2.oid AND
1132 p1.amprocnum > p2.amsupport;
1133 amprocfamily | amprocnum | oid | amname
1134 --------------+-----------+-----+--------
1137 -- Detect missing pg_amproc entries: should have as many support functions
1138 -- as AM expects for each datatype combination supported by the opfamily.
1139 -- GIN is a special case because it has an optional support function.
1140 SELECT p1.amname, p2.opfname, p3.amproclefttype, p3.amprocrighttype
1141 FROM pg_am AS p1, pg_opfamily AS p2, pg_amproc AS p3
1142 WHERE p2.opfmethod = p1.oid AND p3.amprocfamily = p2.oid AND
1143 p1.amname <> 'gin' AND
1144 p1.amsupport != (SELECT count(*) FROM pg_amproc AS p4
1145 WHERE p4.amprocfamily = p2.oid AND
1146 p4.amproclefttype = p3.amproclefttype AND
1147 p4.amprocrighttype = p3.amprocrighttype);
1148 amname | opfname | amproclefttype | amprocrighttype
1149 --------+---------+----------------+-----------------
1152 -- Similar check for GIN, allowing one optional proc
1153 SELECT p1.amname, p2.opfname, p3.amproclefttype, p3.amprocrighttype
1154 FROM pg_am AS p1, pg_opfamily AS p2, pg_amproc AS p3
1155 WHERE p2.opfmethod = p1.oid AND p3.amprocfamily = p2.oid AND
1156 p1.amname = 'gin' AND
1157 p1.amsupport - 1 > (SELECT count(*) FROM pg_amproc AS p4
1158 WHERE p4.amprocfamily = p2.oid AND
1159 p4.amproclefttype = p3.amproclefttype AND
1160 p4.amprocrighttype = p3.amprocrighttype);
1161 amname | opfname | amproclefttype | amprocrighttype
1162 --------+---------+----------------+-----------------
1165 -- Also, check if there are any pg_opclass entries that don't seem to have
1166 -- pg_amproc support. Again, GIN has to be checked separately.
1167 SELECT amname, opcname, count(*)
1168 FROM pg_am am JOIN pg_opclass op ON opcmethod = am.oid
1169 LEFT JOIN pg_amproc p ON amprocfamily = opcfamily AND
1170 amproclefttype = amprocrighttype AND amproclefttype = opcintype
1171 WHERE am.amname <> 'gin'
1172 GROUP BY amname, amsupport, opcname, amprocfamily
1173 HAVING count(*) != amsupport OR amprocfamily IS NULL;
1174 amname | opcname | count
1175 --------+---------+-------
1178 SELECT amname, opcname, count(*)
1179 FROM pg_am am JOIN pg_opclass op ON opcmethod = am.oid
1180 LEFT JOIN pg_amproc p ON amprocfamily = opcfamily AND
1181 amproclefttype = amprocrighttype AND amproclefttype = opcintype
1182 WHERE am.amname = 'gin'
1183 GROUP BY amname, amsupport, opcname, amprocfamily
1184 HAVING count(*) < amsupport - 1 OR amprocfamily IS NULL;
1185 amname | opcname | count
1186 --------+---------+-------
1189 -- Unfortunately, we can't check the amproc link very well because the
1190 -- signature of the function may be different for different support routines
1191 -- or different base data types.
1192 -- We can check that all the referenced instances of the same support
1193 -- routine number take the same number of parameters, but that's about it
1194 -- for a general check...
1195 SELECT p1.amprocfamily, p1.amprocnum,
1198 p4.amprocfamily, p4.amprocnum,
1201 FROM pg_amproc AS p1, pg_proc AS p2, pg_opfamily AS p3,
1202 pg_amproc AS p4, pg_proc AS p5, pg_opfamily AS p6
1203 WHERE p1.amprocfamily = p3.oid AND p4.amprocfamily = p6.oid AND
1204 p3.opfmethod = p6.opfmethod AND p1.amprocnum = p4.amprocnum AND
1205 p1.amproc = p2.oid AND p4.amproc = p5.oid AND
1206 (p2.proretset OR p5.proretset OR p2.pronargs != p5.pronargs);
1207 amprocfamily | amprocnum | oid | proname | opfname | amprocfamily | amprocnum | oid | proname | opfname
1208 --------------+-----------+-----+---------+---------+--------------+-----------+-----+---------+---------
1211 -- For btree, though, we can do better since we know the support routines
1212 -- must be of the form cmp(lefttype, righttype) returns int4.
1213 SELECT p1.amprocfamily, p1.amprocnum,
1216 FROM pg_amproc AS p1, pg_proc AS p2, pg_opfamily AS p3
1217 WHERE p3.opfmethod = (SELECT oid FROM pg_am WHERE amname = 'btree')
1218 AND p1.amprocfamily = p3.oid AND p1.amproc = p2.oid AND
1221 OR prorettype != 'int4'::regtype
1223 OR proargtypes[0] != amproclefttype
1224 OR proargtypes[1] != amprocrighttype);
1225 amprocfamily | amprocnum | oid | proname | opfname
1226 --------------+-----------+-----+---------+---------
1229 -- For hash we can also do a little better: the support routines must be
1230 -- of the form hash(lefttype) returns int4. There are several cases where
1231 -- we cheat and use a hash function that is physically compatible with the
1232 -- datatype even though there's no cast, so this check does find a small
1233 -- number of entries.
1234 SELECT p1.amprocfamily, p1.amprocnum, p2.proname, p3.opfname
1235 FROM pg_amproc AS p1, pg_proc AS p2, pg_opfamily AS p3
1236 WHERE p3.opfmethod = (SELECT oid FROM pg_am WHERE amname = 'hash')
1237 AND p1.amprocfamily = p3.oid AND p1.amproc = p2.oid AND
1240 OR prorettype != 'int4'::regtype
1242 OR NOT physically_coercible(amproclefttype, proargtypes[0])
1243 OR amproclefttype != amprocrighttype)
1245 amprocfamily | amprocnum | proname | opfname
1246 --------------+-----------+----------------+-----------------
1247 435 | 1 | hashint4 | date_ops
1248 1999 | 1 | timestamp_hash | timestamptz_ops
1249 2222 | 1 | hashchar | bool_ops
1250 2223 | 1 | hashvarlena | bytea_ops
1251 2225 | 1 | hashint4 | xid_ops
1252 2226 | 1 | hashint4 | cid_ops
1255 -- Support routines that are primary members of opfamilies must be immutable
1256 -- (else it suggests that the index ordering isn't fixed). But cross-type
1257 -- members need only be stable, since they are just shorthands
1258 -- for index probe queries.
1259 SELECT p1.amprocfamily, p1.amproc, p2.prosrc
1260 FROM pg_amproc AS p1, pg_proc AS p2
1261 WHERE p1.amproc = p2.oid AND
1262 p1.amproclefttype = p1.amprocrighttype AND
1263 p2.provolatile != 'i';
1264 amprocfamily | amproc | prosrc
1265 --------------+--------+--------
1268 SELECT p1.amprocfamily, p1.amproc, p2.prosrc
1269 FROM pg_amproc AS p1, pg_proc AS p2
1270 WHERE p1.amproc = p2.oid AND
1271 p1.amproclefttype != p1.amprocrighttype AND
1272 p2.provolatile = 'v';
1273 amprocfamily | amproc | prosrc
1274 --------------+--------+--------