PostgreSQL analysis now includes 11 new code-quality rules to help teams catch common PL/pgSQL and SQL maintainability issues earlier.
The new rules cover:
-
Composite primary keys with too many columns
-
Overly broad CREATE privileges on schemas
-
Invalid or ambiguous format() strings and placeholders
-
Modification of protected PL/pgSQL automatic variables
-
Use of reserved SQL keywords as identifiers
-
Unused or missing format() arguments
-
Transaction-control statements inside exception handlers
-
Mixing composite and scalar OUT parameters
These checks are available for PostgreSQL projects now in SonarQube Cloud and from SonarQube Server 2026.4.
We’d love your feedback: which PostgreSQL patterns should we prioritize next?