All Errors

PostgreSQL aborts statements that wait too long for locks when lock_timeout is configured. Adjust the timeout value or resolve blocking queries to fix this error.

This error occurs when attempting to store a string or BLOB that exceeds SQLite's maximum allowed size, typically 1 billion bytes by default. It can also trigger when an SQL statement itself is too long.

Serialization failures occur when concurrent transactions conflict in PostgreSQL's Serializable or Repeatable Read isolation levels. Retrying the complete transaction from the beginning is the recommended fix.

The "auth/user-not-found" error occurs when Firebase cannot locate a user account matching the provided email or identifier. This happens when users attempt to sign in with an unregistered account, incorrect email, or after account deletion.

Firebase rejected your phone number format. Phone numbers must be in E.164 format with country code (e.g., +1 650-555-3434). Fix the format or use a valid test number during development.

PostgreSQL aborts transactions when data violates constraints like unique keys, foreign keys, or CHECK rules. Learn to identify which constraint failed, fix data conflicts, and use deferrable constraints to prevent transaction rollbacks.

This error occurs when PostgreSQL cannot find a custom type referenced in a function, procedure, or variable declaration. Common causes include missing schema qualification of custom types, incomplete migrations, enum type naming mismatches, or using non-PostgreSQL-compatible types like STRING instead of TEXT.

The PostgreSQL error 55006 (object_in_use) occurs when you attempt to drop or modify a database object that is currently being accessed by another session. Terminate conflicting connections or wait for the object to become available.

This error occurs when PostgreSQL is in recovery mode (e.g., on a Hot Standby replica), which restricts write operations. The database must either complete recovery or be promoted to primary mode to execute write commands.

This error occurs when you attempt to insert or update a row with a value that already exists in a column marked as UNIQUE. SQLite enforces uniqueness constraints and rejects duplicate values, preventing data inconsistency in your database.

The FAILED_PRECONDITION error occurs when a Firestore operation fails because necessary preconditions (like composite indexes or transaction constraints) are not met. Most commonly caused by missing indexes on compound queries combining where() and orderBy().

A deadlock occurs when two or more transactions wait for each other to release locks, creating a circular dependency. PostgreSQL automatically detects and terminates one transaction to break the deadlock. Fix it by ensuring transactions always access rows in a consistent order.

This error occurs when a user with multi-factor authentication (MFA) enabled tries to sign in. Firebase requires completing the second factor challenge before granting access. Handle this error by catching it and using the MultiFactorResolver to prompt the user for their second factor.

This error occurs when your Firestore security rules deny access to the requested resource. Fix it by reviewing and updating your security rules to allow authenticated users or by ensuring the user is properly logged in before accessing the database.

This error occurs when you try to create or update a record with a foreign key value that doesn't match any primary key in the referenced table. Verify the referenced record exists and check for data type mismatches between your schema and database.

PostgreSQL runs out of shared memory when the lock table exceeds capacity, typically due to excessive table locking or high concurrency. Increase max_locks_per_transaction or adjust connection settings to resolve.

The functions/permission-denied error occurs when your Cloud Function lacks IAM permissions to access other Firebase services. This is typically caused by missing or insufficient Cloud IAM roles assigned to the service account running your function.

PostgreSQL enforces a hard limit of 1,600 columns per table. This error occurs when you exceed that limit or hit the 1,664-column tuple limit in SELECT statements. Redesign your schema using arrays, JSON, or table partitioning.

The DEADLINE_EXCEEDED error occurs when a Firestore operation exceeds the default 60-second timeout window. This commonly happens with large batch operations, complex queries, or high-volume read/write operations. Fix it by optimizing queries, breaking operations into smaller chunks, and addressing latency issues.

PostgreSQL raises error 54000 when a query or schema surpasses built-in limits such as maximum columns per table, index key size, or expression nesting depth. Resolve by restructuring your schema, simplifying queries, or breaking down large operations.