Tag: PostgreSQL

Problems with PostgreSQL

ID	Title	Description	Category	Technology	Tags
CRE-2025-0042 Critical Impact: 7/10 Mitigation: 5/10	PostgreSQL transaction fails with deadlock detected error in psycopg2 and Django	- Applications using Django with PostgreSQL and psycopg2 may encounter `deadlock detected` errors under concurrent write-heavy workloads. - PostgreSQL raises this error when two or more transactions block each other cyclically while waiting for locks, and one must be aborted. - Django surfaces this as an `OperationalError`, and the affected transaction is rolled back.	Database Problems	django	PostgreSQL Psycopg2 Django Transaction Deadlock Operational error Public Known Issue
CRE-2025-0078 High Impact: 10/10 Mitigation: 2/10	SpiceDB Database Schema Failures: Missing Core Tables	Detects critical SpiceDB database schema failures caused by missing core tables like `metadata`, `alembic_version`, or `relation_tuple_transaction`. These errors often stem from incomplete migrations, startup race conditions, or schema corruption, resulting in a complete breakdown of SpiceDB authorization capabilities.	Authorization Systems	spicedb	SpiceDB Migration Failure Schema Error PostgreSQL
CRE-2025-0079 Critical Impact: 10/10 Mitigation: 3/10	SpiceDB Database Corruption: Critical Table Loss	Detects catastrophic SpiceDB database corruption where critical core tables like `alembic_version` and `relation_tuple_transaction` are missing or dropped. This represents complete database corruption that renders SpiceDB unable to perform any authorization operations, causing total permission system failure.	Authorization Systems	postgresql	SpiceDB Database Corruption Authorization PostgreSQL
CRE-2025-0081 Critical Impact: 9/10 Mitigation: 8/10	Temporal Server Fails Persistence on Read-Only Database	Detects critical failures where Temporal Server is unable to perform essential database write operations (e.g., starting workflows, recording history, completing tasks) because its underlying SQL database (e.g., PostgreSQL) is in a read-only state. This leads to a halt or severe degradation in workflow processing and can cause cluster instability.	Temporal Server Failure	temporal	Temporal PostgreSQL READONLY
CRE-2025-0130 High Impact: 9/10 Mitigation: 3/10	Supabase Self-Hosted: Postgres Container Fails to Start Due to Port Conflict	Detects when Supabase self-hosted Postgres container fails to start because another service is already using port 5432. This is a common issue during initial setup or when multiple Postgres instances are running on the same host. The failure prevents the entire Supabase stack from starting properly.	Database Problems	supabase	Supabase PostgreSQL Port Binding Configuration Startup Failure Self-Hosted Container Crash Public
CRE-2025-0132 Medium Impact: 8/10 Mitigation: 5/10	Supabase Self-Hosted: Database Connection Timeout and Service Failure	Detects when Supabase services lose connection to the PostgreSQL database due to timeouts, network issues, or database unavailability. This affects Auth, REST API, Storage, and all database-dependent operations. Occurs during database restarts, network partitions, or when database becomes unresponsive.	Database Problems	supabase	Supabase PostgreSQL Connection Timeout Network Self-Hosted Connectivity Public
CRE-2025-0135 Medium Impact: 7/10 Mitigation: 6/10	Supabase Self-Hosted: Database Migration Failures Due to SQL Syntax Errors	Detects when Supabase database migrations fail due to SQL syntax errors, invalid schema changes, or constraint violations. Migration failures can leave the database in an inconsistent state and prevent the application from starting or functioning properly.	migration-failure	postgresql	Supabase PostgreSQL Migration Failure Schema Error Self-Hosted Configuration Public
CRE-2025-0141 High Impact: 10/10 Mitigation: 7/10	Supabase Self-Hosted: Disk Full During Database Migration Operations	Detects when Supabase PostgreSQL database operations fail due to insufficient disk space during migrations, data imports, or large transactions. This can corrupt the database, leave migrations in inconsistent state, and cause complete service failure requiring manual intervention.	Storage	supabase	Supabase PostgreSQL Disk Full Storage Migration Failure WAL Self-Hosted Critical Failure Data Loss Risk Public