The list of all the queries

Wrong comment - trigger function does not implement a database operation

Query goal: Trigger functions should not contain references to database operations. Perhaps the trigger implements ensuring some invariant of the operation but it does not implement the operation itself.
Notes about the query: The query assumes that database operations are in the form OP. In the returned body of routine the query replaces each newline character with the line break (br) tag for the better readability in case the query result is displayed in a web browser. There could be multiple routines with the same name but with different parameters in the same schema (overloading). Thus, for the unique identification of the routine it is necessary to present also its parameters in addition to the schema name and routine name.
Query type: Problem detection (Each row in the result could represent a flaw in the design)
Query reliability: High (Few or no false-positive results)
Query license: MIT License
Fixing suggestion: Remove references to the database operation from the comment.
Data source: INFORMATION_SCHEMA+system catalog
SQL query: Click on query to copy it

SELECT 
  n.nspname AS routine_schema, 
  p.proname AS routine_name,
  pg_get_function_identity_arguments(p.oid) AS parameters,
  d.description AS comment,  
  regexp_replace(p.prosrc,'[\r\n]','<br>','g')  AS func_src
FROM 
  (pg_catalog.pg_proc p JOIN pg_catalog.pg_namespace n ON p.pronamespace = n.oid) JOIN pg_catalog.pg_type t ON p.prorettype=t.oid
  LEFT JOIN pg_catalog.pg_description d ON p.oid=d.objoid
WHERE 
 p.proname NOT IN ('f_assume_you_must_use_files', 'f_check_format_comma_separated_list', 'f_check_password', 'f_default_value_with_no_match') AND
   n.nspname NOT IN (SELECT schema_name
FROM INFORMATION_SCHEMA.schemata
WHERE schema_name<>'public' AND
schema_owner='postgres' AND schema_name IS NOT NULL) AND t.typname='trigger' AND 
d.description~*'^.*([[:space:]]*|")OP[[:space:]]*[[:digit:]].*$'
ORDER BY routine_schema, routine_name, parameters;

Collections where the query belongs to

Collection nameCollection description
Find problems automaticallyQueries, that results point to problems in the database. Each query in the collection produces an initial assessment. However, a human reviewer has the final say as to whether there is a problem or not .

Categories where the query belongs to

Category nameCategory description
Comfortability of database evolutionQueries of this category provide information about the means that influence database evolution.
CommentsQueries of this category provide information about comments to the database objects that have been registered in the system catalog.
Triggers and rulesQueries of this category provide information about triggers and rules in a database.
User-defined routinesQueries of this category provide information about the user-defined routines

Reference materials for further reading

Reference
Writing contracts of database operations is an example of using the design by contract approach for specifying software. https://en.wikipedia.org/wiki/Design_by_contract

The list of all the queries