Tag: PostgreSQL

Problems with PostgreSQL

ID	Title	Description	Category	Technology	Tags
prequel-2025-0028 Low Impact: 2/10 Mitigation: 2/10	Datadog Postgres Check Exception	The Datadog Agent’s Postgres integration throws an uncaught Python traceback while trying to run an `EXPLAIN (FORMAT JSON)` against a sampled query. After the first failure the underlying psycopg2 cursor is closed, and every subsequent collection cycle logs ``` Traceback … File \".../datadog_checks/postgres/explain_parameterized_queries.py\", … psycopg2.InterfaceError: cursor already closed ``` The check status flips to ERROR, and query metrics / samples stop flowing.	Postgres Problems	datadog	PostgreSQL Datadog
prequel-2025-0084 Medium Impact: 7/10 Mitigation: 4/10	PostgreSQL unsupported Unicode escape sequence error	The application encounters errors when PostgreSQL attempts to process strings containing invalid or unsupported Unicode escape sequences. This commonly occurs in applications using psycopg2 to interact with PostgreSQL databases, resulting in queries failing with \"unsupported Unicode escape sequence\" errors. The underlying issue is that PostgreSQL's string parser attempts to interpret escape sequences like '\\\\uXXXX' according to Unicode standards, but rejects malformed or incomplete sequences.	Database Problems	python	PostgreSQL Unicode Data Error
prequel-2025-0086 Medium Impact: 7/10 Mitigation: 3/10	Database Not-Null Constraint Violation	An application is attempting to insert or update records in a database table with NULL values in columns that have NOT NULL constraints. This causes database operations to fail with integrity errors, typically surfacing as NotNullViolation exceptions in application logs. In Django applications, this commonly appears as django.db.utils.IntegrityError or psycopg2.errors.NotNullViolation when using PostgreSQL.	Database Integrity Problems	psycopg2	Database PostgreSQL Django Data Integrity