Postgres error 0A000: feature not supported
feature not supported
The statement asks for something Postgres (or this server configuration) does not implement.
Common causes
- Using a feature in a context that does not allow it, for example a set-returning function where it is not allowed, or FOR UPDATE with GROUP BY.
- Statements a connection pooler in transaction mode cannot carry across transactions, such as session-level advisory locks or LISTEN.
- Altering a column type that a view or rule depends on.
How to fix it
- Read the full message: it names the unsupported part. Rewrite the query around it (for example lock rows in a subquery, then aggregate).
- Use a session-mode or direct connection for features that need a persistent session.
- Drop and recreate dependent views around a column type change.
Through a REST API
PostgREST, the REST layer behind supabase-js and Scribase, answers HTTP 400 for this error and returns the SQLSTATE in the code field of the JSON error body.
Questions
What does Postgres error 0A000 mean?
0A000 is feature_not_supported in class 0A (Feature Not Supported). The statement asks for something Postgres (or this server configuration) does not implement.
How do I fix 0A000?
Read the full message: it names the unsupported part. Rewrite the query around it (for example lock rows in a subquery, then aggregate). Use a session-mode or direct connection for features that need a persistent session. Drop and recreate dependent views around a column type change.
What HTTP status does a REST API return for 0A000?
PostgREST, the REST layer behind supabase-js, answers 400.