Skip to main content

Tag: PostgreSQL

Problems with PostgreSQL

IDTitleDescriptionCategoryTechnologyTags
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 ProblemsdjangoPostgreSQLPsycopg2DjangoTransactionDeadlockOperational errorPublicKnown Issue
CRE-2025-0078
High
Impact: 10/10
Mitigation: 2/10
SpiceDB Database Schema Failures: Missing Core TablesDetects 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 SystemsspicedbSpiceDBMigration FailureSchema ErrorPostgreSQL
CRE-2025-0079
Critical
Impact: 10/10
Mitigation: 3/10
SpiceDB Database Corruption: Critical Table LossDetects 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 SystemspostgresqlSpiceDBDatabase CorruptionAuthorizationPostgreSQL
CRE-2025-0081
Critical
Impact: 9/10
Mitigation: 8/10
Temporal Server Fails Persistence on Read-Only DatabaseDetects 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 FailuretemporalTemporalPostgreSQLREADONLY