All Errors

This error occurs when multiple simultaneous requests try to modify the same database rows. Supabase uses PostgreSQL's SERIALIZABLE isolation level, which detects these conflicts and rejects one transaction to maintain data integrity.

This error occurs when attempting to sign up, link, or update a phone number that is already associated with another user account in Supabase Auth. This can happen during signup, MFA enrollment, or when updating user phone numbers.

Supabase throws this error when you attempt OAuth signup with a provider that hasn't been enabled in your project settings. Enable the provider in the Supabase dashboard and verify credentials are correct.

This error occurs when you attempt to use GET STACKED DIAGNOSTICS outside of an exception handler block in PL/pgSQL. GET STACKED DIAGNOSTICS can only be called within an EXCEPTION WHEN clause to retrieve diagnostic information about the current exception.

Firebase Cloud Storage uses the gs:// protocol for references. This error occurs when you use an incorrect URL format (like HTTP URLs) instead of gs://bucket-name/path. Fix it by using the correct reference method.

A Redis transaction was aborted due to syntax errors or WATCH key modifications, and you attempted to queue more commands after the abort. Clear the transaction state with DISCARD and verify your commands.

The NTH_VALUE window function received an invalid argument for the row position parameter. The second argument must be a positive integer greater than zero.

Cardinality violation occurs when a query returns multiple rows in a context that expects a single row, such as in a subquery used with comparison operators or in an ON CONFLICT DO UPDATE statement.

The XML data being processed is malformed or contains invalid structures that the PostgreSQL XML parser cannot handle. This commonly occurs with DOCTYPE declarations, oversized text nodes, or special characters in COPY operations.

SQLSTATE 22022 occurs when an indicator variable or parameter is not large enough to hold the value being returned from a query or stored procedure. This typically happens in embedded SQL or driver-level parameter handling where indicator parameters are used to signal NULL values or data length information.

PostgreSQL error 22019 occurs when an invalid escape character is used in a LIKE pattern or string literal. This typically happens when the escape character in a LIKE ESCAPE clause is longer than one character or when backslash escapes are used incorrectly.

This error occurs when using a RANGE frame in a MySQL window function without a numeric or temporal ORDER BY column. Window frames with RANGE boundaries require numeric or date/time types to define the range offset.

SQLSTATE 01007 is a warning that PostgreSQL raises when a GRANT statement attempts to assign privileges that you don't have authority to grant. The operation completes but signals that the requested privilege was not actually granted, helping you identify permission management issues in your scripts.

This error occurs when attempting to upload a file to Supabase Storage at a path where a file already exists. By default, Supabase rejects file uploads that would overwrite existing resources. The solution is to enable the upsert option to allow file replacement or delete the existing file first.

PostgreSQL raises HV007 when a foreign-data wrapper encounters a column name that does not exist on the remote data source. This typically occurs due to case sensitivity mismatches, incorrect column_name mappings, or remote table schema changes. Verifying column names and updating the foreign table definition to match the remote schema resolves the error.

The auth/missing-uid error occurs when using the Firebase Admin SDK to perform user operations (like createUser, getUser, updateUser, or setCustomUserClaims) without providing a valid UID parameter. This error indicates that a required user ID identifier is missing or empty.

The PostgreSQL 42P14 error occurs when creating a prepared statement with syntax errors, mismatched parameter types, or invalid SQL. This prevents the server from parsing and caching the prepared statement, requiring corrections to the SQL definition.

PostgreSQL error 42501 indicates insufficient privileges to access a table, commonly caused by missing RLS policies, incorrect grants, or authentication issues in Supabase. This error occurs when your application tries to read, insert, or update data without proper permissions configured.

Error 2 (EE_READ) occurs when MySQL cannot read a file it needs to access, typically due to file permissions, missing files, or filesystem issues. This error prevents database operations and requires checking file access rights and data integrity.

The "ERR Failed to resolve hostname" error occurs when Redis or a Redis client cannot resolve a hostname to its IP address through DNS. This is typically caused by DNS configuration issues, network connectivity problems, or incorrect hostname configuration.