PostgreSQL Query Catalog

Find domains that are not used in case of any base table column and routine (input or otput) parameter (as their type). Do not keep in your database elements that are not needed by anybody. These should be put in use or dropped, otherwise these are dead code.

Find enumerated types that are not used in case of any base table column, domain, and routine (input or otput) parameter (as their type). Do not keep in your database elements that are not needed by anybody. These should be put in use or dropped, otherwise these are dead code.

Find foreign data wrappers that do not have any associated foreign servers.

Find foreign servers that do not have any associated foreign tables.

Find indexes that are not used by the DBMS. Remember that indexes are not a "free lunch" and they slow down the processes of updating data.

Find indexes that are not used by the DBMS. Remember that indexes are not a "free lunch" and they slow down the processes of updating data.

Find named input parameters that are not referenced in the routine body. All the parameters that are presented in the routine signature declaration must be used in its body. Otherwise these are dead code elements.

Do not keep in your database elements that are not needed by anybody. These should be put in use or dropped, otherwise these are dead code.

Do not keep in your database elements that are not needed by anybody. These should be put in use or dropped, otherwise these are dead code.

Find triggers that try prevent updating data in a certain column but prevent also certain legal updates - updates that write to a field a value that was in the field before the update.

Find all UPDATE triggers. Make sure that they specify a correct set of columns in which data modification will fire the trigger.

Find UPDATE triggers where updated columns are not specified. These triggers could be executed too often because unneeded executions are not prevented.

Find UPDATE triggers where WHEN clause is not specified. These triggers could be executed too often because unneeded executions are not prevented.

Find for each derived table the list of base tables that are used by the derived table.

Find indexes that are used by the DBMS.

Be precise and write as little code as possible. Prefer expressions with simple invocations of functions like localtimestamp, current_timestamp, and current_date over expressions like (now())::date. Find table columns that have a default value that casts the type of the returned value of a non-deterministic function (now, localtimestamp, current_timestamp, and current_date).

Find columns and parameters where the type of the identifier is perhaps explicitly indicated in the name.

Find columns and parameters where the type of the identifier is perhaps explicitly indicated in the name.

Find composite types that are created by a user, i.e., the type is not created automatically by the database management system based on a relation.

Find user-defined views and materialized views. Pay attention to the outer join operations. One should use these if and only if there is a real need for them. Otherwise they just reduce performance. On the other hand, pay attention that outer join is used where it is logically needed.