PostgreSQL Query Catalog

This metric represents the number of foreign keys in a base table.

Find how many base tables are referenced from a base table by using foreign keys.

"Names in software are 90 percent of what make software readable. You need to take the time to choose them wisely and keep them relevant. Names are too important to treat carelessly. Names should not cause confusion." (Robert C. Martin, Clean Code) Names should be expressive. Find the TOP 3 longest (identifiers) names of user-defined objects by their type. These could be the first candidates of renaming in order to give to database objects better names.

Find the longest referential paths between the tables regardless of the schema that contain the tables.

Find the number and percentage of base tables where all the non-primary key columns are optional

Find the extent in which data integrity is checked at the database level. Find the number and percentage of base tables that do not have any associated CHECK constraints.

Find the extent in which repeating rows are permitted in the database. Find the number and percentage (from the total number of base tables) of base tables that do not have the PRIMARY KEY constraint and also do not have any UNIQUE constraints.

Names should be expressive. Find the number of different names used in a database as well as the number of named database objects, and the percentage of different names from all the names. Names should be expressive. Different objects should have different names. The smaller the percentage the less descriptive are the names in the database. Find the number of different names (identifiers) of user-defined database objects and compare it with the total number of database objects. The values could be used to compare different databases.

"Names in software are 90 percent of what make software readable. You need to take the time to choose them wisely and keep them relevant. Names are too important to treat carelessly. Names should not cause confusion." (Robert C. Martin, Clean Code) Names should be expressive. Different objects should have different names. The smaller the percentage the less descriptive are the names in the database. Find the number of different names (identifiers) of user-defined database objects by the object type and compare it with the total number of database objects with this type. The values could be used to compare different databases.

Find the number and percentage of optinal columns in base tables

Find the number of base table columns based on data type.

Find the number of base table columns based on the category of data type that the columns have.

Find the total number of columns in the different types of tables as well as average number of columns in the tables as well as minimal and maximal number of columns.

Find the number of commented routines based on the way how the comments have been added (as a COMMENT object or as a comment in the routine body).

Find the number of compensating actions that are specified in case of foreign key constraints.

Find the number of constraints in different schemas. The number of constraints in a database gives an indication about the state of enforcing constraints at the database level.

Find the total number of columns with a default value as well as the number of columns with different kinds of default values (the number of columns where the default is used to implement surrogate key, the number of columns where the default is not used to implement surrogate key, the number of columns with a static default value, the number of columns with a dynamic default value).

Find the number of derived table columns with json, xml, array, or user-defined types. Such columns may contain data that has been aggregated/composed based on values in base tables.

Find the number of direct and all (direct+indirect) child tables of a base table based on the foreign keys. The result may help to classify the data. If the number of direct children is small but the number of all children is large, then the table probably contains classifiers. If both the number of direct and all children is large, then the table probably contains master data. If the number of all children is small, then the table probably contains transactional data, logs, or descriptive information of main entities.

Find the number of direct and all (direct+indirect) child tables of a base table based on the table inheritance.