You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: dblinter/default_config.yaml
+8-9Lines changed: 8 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ base:
53
53
coef: 5
54
54
resource_gain: Primary keys ensure no duplicates are present in the table.
55
55
risk_impact: Duplicate rows possible, breaking data integrity. Replication failures, inefficient updates requiring full table scans. Severe performance degradation on large tables and logical replication issues.
56
-
- name: HowManyRedudantIndex
56
+
- name: HowManyRedundantIndex
57
57
ruleid: B002
58
58
enabled: True
59
59
params:
@@ -77,9 +77,9 @@ base:
77
77
desc: Count number of tables without index on foreign key.
78
78
message: "{0} table without index on foreign key exceed the warning threshold: {1}%. Object list [{2}]"
risk_impact: Extremely slow JOIN queries and cascade operations. DELETE/UPDATE on parent tables can lock child tables for extended periods, causing application timeouts and severe performance issues.
84
84
- name: HowManyUnusedIndex
85
85
ruleid: B004
@@ -216,8 +216,8 @@ table:
216
216
ruleid: T010
217
217
enabled: True
218
218
context:
219
-
desc: A table, his column or indexes use reserved keywords.
resource_gain: Adding appropriate indexes to high-seqscan tables will improve query performance and reduces I/O load, freeing resources for other queries.
237
+
resource_gain: Adding appropriate indexes to high-seqscan tables improves query performance and reduces I/O load, freeing resources for other queries.
238
238
risk_impact: High sequential scan rates indicate missing indexes, causing severe performance issues. Full table scans consume excessive memory and I/O, potentially causing OOM errors and impacting all database users.
239
239
- name: TableWithSensibleColumn
240
240
ruleid: T012
@@ -246,13 +246,13 @@ table:
246
246
- Install extension PostgreSQL Anonymizer, and create some masking rules on
247
247
coef: 1
248
248
resource_gain: Proper data classification and masking reduces compliance audit time. Enables safe data sharing for development and testing environments.
249
-
risk_impact: GDPR/CCPA compliance violations risk with fines. Unprotected PII exposure in logs, backups, and non-production environments. Severe reputational damage risk.
249
+
risk_impact: Risk of GDPR/CCPA compliance violations with fines. Unprotected PII exposure in logs, backups, and non-production environments. Severe reputational damage risk.
250
250
schema:
251
251
- name: SchemaWithDefaultRoleNotGranted
252
252
ruleid: S001
253
253
enabled: True
254
254
context:
255
-
desc: The schema ha no default role. Means that futur table will not be granted through a role. So you will have to re-execute grants on it.
255
+
desc: The schema has no default role. Means that future tables will not be granted through a role. So you will have to re-execute grants on it.
256
256
message: "No default role granted on schema {0}.{1}. It means that each time a table is created, you must grant it to roles."
257
257
fixes:
258
258
- "Add a default privilege=> ALTER DEFAULT PRIVILEGES IN SCHEMA <schema> for user <schema's owner>"
risk_impact: Complex and error-prone environment refresh procedures. Risk of broken references, failed migrations, and extended downtime during refresh operations. Potential data integrity issues.
0 commit comments