All Errors

This error occurs in AWS RDS for PostgreSQL when a user without rds_superuser privileges attempts to install an extension. In RDS versions 13+, most extensions can be installed by users with CREATE database privileges, but some require elevated permissions. The fix depends on your RDS version and whether you can use delegated extension management.

Prisma surfaces P2034 when a transaction cannot commit because the database detected a write conflict or deadlock during the commit phase. Retry the transaction with Serializable isolation, a bounded retry loop, and less contention on the affected rows to let the operation finish successfully.

This error occurs when attempting to unlink or delete a user's only authentication identity in Supabase. Users must have at least one identity to maintain account access.

PostgreSQL rejects new connections when the max_connections limit is reached. Fix this by tuning max_connections, implementing connection pooling with PgBouncer, or terminating idle sessions.

This error occurs when attempting to execute write operations in a read-only subtransaction or savepoint, or when the access mode conflicts between a parent transaction and its branch.

PostgreSQL encounters a disk full error when the file system runs out of available space. This prevents writes and can cause database shutdown. Immediate action is needed to free space or expand storage.

PostgreSQL autovacuum is performing an emergency VACUUM operation to freeze old transaction IDs and prevent transaction ID wraparound, which could cause database shutdown if not addressed.

Supabase rejects password updates where the new password string matches the existing one and responds with "same_password: New password must be different." The API re-authenticates the submitted password before writing, so the request finishes with HTTP 422 whenever both values align.

This error occurs when Elasticsearch security features fail to authenticate a user due to incorrect credentials, misconfigured security realms, expired certificates, or disabled security settings. It commonly appears when connecting to secured Elasticsearch clusters with invalid usernames, passwords, or authentication tokens.

PostgreSQL forbids window functions like ROW_NUMBER(), RANK(), or SUM() OVER() in WHERE clauses because window functions execute after WHERE filters. To filter based on window function results, compute them in a subquery or CTE first, then apply your WHERE condition in the outer query.

The "Cache lookup failed for type" error occurs when PostgreSQL cannot find a data type with a specific OID (Object Identifier) in its internal system catalog cache. This typically happens after types or schemas have been dropped and recreated while connections remain active. The cache mismatch causes queries and functions to fail until connections are reset or the application is restarted.

The "mfa_verification_failed: MFA verification failed" error occurs when Supabase Auth cannot verify a multi-factor authentication code. This typically happens due to incorrect TOTP codes, timing synchronization issues, expired codes, or rate limiting from too many failed verification attempts.

The "Cache lookup failed for function" error occurs when PostgreSQL cannot find a function in its system catalog (pg_proc). This typically happens after dropping and recreating functions while active connections reference the old function, or in cases of system catalog corruption.

The Prisma P3004 error occurs when attempting to run migrations against a reserved system database like "mysql", "postgres", or "information_schema". This prevents accidental corruption of critical database infrastructure. The fix requires connecting to a user-created application database instead.

Redis returns `NOPROTO sorry, this protocol version is not supported` when a client tries to negotiate an unsupported protocol version during the HELLO handshake, typically when requesting RESP3 on a server that only supports RESP2. Modern clients auto-negotiate to RESP3 by default, but older Redis versions or disabled RESP3 configurations reject this upgrade. This guide explains the protocol mismatch, common scenarios, and how to downgrade or enable the correct protocol version.

Prisma error P2026 occurs when your query uses a database feature that is not supported by your current database provider. Common examples include full-text search on SQLite, certain index types on MySQL, or advanced constraints not available in all databases.

The 39P02 error occurs when a set-returning function (SRF) or table function violates PostgreSQL's internal protocol requirements, typically when the function doesn't properly implement the expected return mode or fails to follow the correct sequence for returning multiple rows.

Heroku PostgreSQL plans have connection limits (20 for Essential, 120+ for Standard). When your application opens too many connections without reusing them, you hit this limit. Fix it by implementing connection pooling with pgBouncer, reducing your connection pool size, or upgrading your plan.

The "Cannot find module 'mongoose'" error occurs when Node.js cannot locate the mongoose package in your project. This typically happens when mongoose is not installed, was installed in the wrong location, or when the node_modules directory is missing or corrupted. The error prevents your application from importing mongoose for MongoDB operations.

This error occurs when you attempt to calculate the logarithm of zero, a negative number, or provide an invalid base argument to PostgreSQL logarithmic functions like LOG(), LN(), or LOG10(). Logarithms are only mathematically defined for positive numbers.