# Postgres error 26000: prepared statement "x" does not exist

> The driver tried to execute a named prepared statement that this server connection never saw.

Source: https://scribase.com/postgres-errors/26000

SQLSTATE class: Invalid SQL Statement Name. Over PostgREST/supabase-js this maps to HTTP 400.

## Causes

- Transaction-mode pooling: the statement was prepared on one server connection and executed on another.
- DISCARD ALL or a reconnect cleared prepared statements the driver still remembers.

## Fixes

- Disable named prepared statements in the driver behind a transaction pooler.
- Use session-mode or direct connections for that client.