| 201 |
Base table columns with CITEXT type |
Find base table columns with CITEXT type and make sure that case insensitivity is really needed in case of this column. |
General |
system catalog base tables only |
2020-11-06 14:51 |
MIT License |
View |
| 202 |
Base table columns with DECIMAL (p, s) or NUMERIC (p, s) type |
Find base table columns with DECIMAL (p, s) or NUMERIC (p, s) type and make sure that precision p and scale s are not too big or too small. |
General |
INFORMATION_SCHEMA only |
2020-11-06 14:51 |
MIT License |
View |
| 203 |
BOOLEAN base table and foreign table columns with a PRIMARY KEY, UNIQUE, or FOREIGN KEY constraint that involves olnly this column |
Find base table columns with the Boolean type that has a PRIMARY KEY, UNIQUE, or FOREIGN KEY constraint that involves only this column. Avoid unnecessary constraints. It is quite improbable that there must be such constraints. For instance, a table with PRIMARY KEY () or UNIQUE () constraint can have at most two rows. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2022-11-03 10:46 |
MIT License |
View |
| 204 |
Do not use the money data type |
Find base table columns with the Money data type. Each value of the money type has associated currency sign that depends on server settings. It could be $. Moreover, using the values for arithmetic operations requires casts that makes the code more complicated. |
Problem detection |
INFORMATION_SCHEMA only |
2021-02-25 17:29 |
MIT License |
View |
| 205 |
Tsvector values are not automatically calculated |
Find base table columns with tsvector type in case of which it is not a generated column nor does the table has an associated trigger to calculate the tsvector value automatically. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-11-07 11:45 |
MIT License |
View |
| 206 |
Base table column of national identification numbers has a too short field size |
Find base table columns with VARCHAR type that name refers to the possibility that these are used to register national identification numbers (personal codes). Find the columns where the field size is shorter than 20. |
Problem detection |
INFORMATION_SCHEMA only |
2021-02-25 17:29 |
MIT License |
View |
| 207 |
Candidate keys where all columns have a static default value |
Find base table primary key and unique constraints where all columns probably have a static default value. Candidate key columns (columns that belong to the primary key or to an unique constraints) shouldn't have static default values unless you are enforcing a rule that a table can have at most one row. The point of default values is that system assigns them automatically. There cannot be multiple rows with the same key value. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-11-12 11:33 |
MIT License |
View |
| 208 |
At most one row is permitted in a table (based on check constraints) |
Find base tables and foreign tables where based on a check constraint, a key constraint, and a NOT NULL constraint can be at most one row. Make sure that this is the real intent behind the constraint, not a mistake. Find tables where a check constraint permits only one possible value in a column, the column has NOT NULL constraint, and constitutes a key, i.e., has the PRIMARY KEY or UNIQUE constraint. |
General |
INFORMATION_SCHEMA+system catalog base tables |
2022-11-03 15:21 |
MIT License |
View |
| 209 |
At most one row is permitted in a table (based on enumeration types) |
Find base tables and foreign tables where based on the type of a column, a key constraint, and a NOT NULL constraint can be at most one row. Make sure that this is the real intent behind the constraint, not a mistake. Find tables where a column has an enumeration type with exactly one value, the column has NOT NULL constraint, and constitutes a key, i.e., has the PRIMARY KEY or UNIQUE constraint. |
General |
INFORMATION_SCHEMA+system catalog base tables |
2022-11-03 15:18 |
MIT License |
View |
| 210 |
Base tables and materialized views without any index |
Find base tables and materialized views that do not have any index. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-11-05 19:39 |
MIT License |
View |
| 211 |
Base table columns permitting temporal values that may be outside the range of logical values |
Find base tables columns with temporal types (date and timestamp) that do not belong to a foreign key and that do not have any associated simple CHECK constraints, i.e., constraint that involves only one column. For instance, in the column registration_time that does not have any associated CHECK constraints could be values '1200-01-01 00:00' or '5900-12-31 00:00'. Rows with these values most probably represent wrong propositions and the system should restrict registration of such data. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-17 00:40 |
MIT License |
View |
| 212 |
FILLFACTOR is probably too big |
Find base tables in case of which the FILLFACTOR property has perhaps a too big value. Try to find base tables that probably encounter UPDATE operations. In the tables that have frequent updates you want to have free space in table pages (blocks) to accommodate new row versions, which the system automatically creates as a result of fulfilling UPDATE statements. If a new row version will be put to another page by the system, then it means that table indexes have to be updated as well. Thus, the more there are indexes, the more the table would benefit from keeping a new row version in the same page as the old version. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2024-11-21 09:19 |
MIT License |
View |
| 213 |
Minimum tuple length required before trying to move long column values into TOAST tables has been changed |
Find base tables in case of which toast_tuple_target storage parameter value is not the default value (2040). "Changing this value may not be useful for very short or very long rows. Note that the default setting is often close to optimal, and it is possible that setting this parameter could have negative effects in some cases. " Make sure that the parameter has an optimal value. |
General |
INFORMATION_SCHEMA+system catalog base tables |
2020-11-06 14:51 |
MIT License |
View |
| 214 |
Base tables where certainly registration time is not recorded |
Find base tables that do not have any column with a timestamp type. In such tables certainly registration time is not recorded. Make sure as to whether recording registration time is necessary. |
General |
INFORMATION_SCHEMA only |
2021-02-26 00:41 |
MIT License |
View |
| 215 |
Base tables that do not have a TOAST table |
Find base tables that (due to the types of their columns) do not have an associated TOAST table for storing out-of-line data. |
General |
system catalog base tables only |
2020-11-06 14:51 |
MIT License |
View |
| 216 |
Base tables with plenty of data |
Find base tables that have 1000 rows or more. |
General |
system catalog base tables only |
2022-10-21 11:25 |
MIT License |
View |
| 217 |
Perhaps last update time trigger is missing |
Find base tables that have a column for last update time but the table does not have associated before update row level trigger for changing the last update time. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2023-12-30 15:22 |
MIT License |
View |
| 218 |
Perhaps a CHECK constraint about the combination of truth values is missing |
Find base tables that have at least two columns that have Boolean type and have at least one Boolean column that is not covered by a CHECK constraint involving more than one Boolean column. The Boolean columns possibly mean that we want to record data about states. Often the states depend on each other. For instance, if an order is archived it must be inactive. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-02-25 17:29 |
MIT License |
View |
| 219 |
Perhaps a CHECK constraint about the order of events is missing |
Find base tables that have at least two columns that have DATE or TIMESTAMP (with or without time zone) type and do not have any associated CHECK constraint that involves two or more of these columns. The columns mean that we want to record data about events or processes, which often have a certain order. Hence, in case of each row of such a table the values in these columns must be in a certain order. For instance, the end of a meeting cannot be earlier than the beginning of the meeting. |
Problem detection |
INFORMATION_SCHEMA+system catalog base tables |
2021-02-25 17:29 |
MIT License |
View |
| 220 |
Base tables created based on a type |
Find base tables that have been created based on a composite type and thnk through as to whether it was really needed. |
General |
system catalog base tables only |
2020-11-06 14:51 |
MIT License |
View |