Goal Find names of rules that are used within the same schema more than once. Give different triggers different names.
Type Problem detection Each row in the result could represent a flaw in the design
Reliability High Few or no false-positive results
License MIT (opens in new tab)
Fixing Suggestion Give to rules unique names within a schema. Use table name in the rule name. Follow a naming convention.
Data Source system catalog only
SQL Query 
SELECT rulename, schemaname, Count(*) AS number_of_occurrences, string_agg(tablename, ';<br>' ORDER BY tablename) AS tables
FROM pg_rules
GROUP BY rulename, schemaname
HAVING Count(*)>1
ORDER BY Count(*) DESC, schemaname, rulename;

Collections

This query belongs to the following collections:

Find problems automatically

Queries, 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 .

NameDescription
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

This query is classified under the following categories:

Comfortability of database evolution

Queries of this category provide information about the means that influence database evolution.

Naming

Queries of this category provide information about the style of naming.

Triggers and rules

Queries of this category provide information about triggers and rules in a database.

NameDescription
Comfortability of database evolutionQueries of this category provide information about the means that influence database evolution.
NamingQueries of this category provide information about the style of naming.
Triggers and rulesQueries of this category provide information about triggers and rules in a database.