PostgreSQL: current transaction is aborted
ERROR: current transaction is aborted, commands ignored until end of transaction blockAn earlier statement in this transaction failed, and Postgres now rejects every following statement until you roll back. The real problem is that first error; find it, then roll back and retry.
What this error means
Once any statement in a transaction errors, Postgres marks the whole transaction as failed. It will not run anything else until you issue ROLLBACK (or roll back to a savepoint), so every following statement returns this message.
This error is a symptom, not the cause. The statement that originally failed, earlier in the block, is what you actually need to fix.
How to fix it
You want to recover the session
Roll back to end the failed transaction, then start again.
ROLLBACK;You want to continue past a failing statement
Wrap risky statements in a savepoint so one failure does not poison the whole transaction.
SAVEPOINT s1;
-- risky statement here
-- if it fails:
ROLLBACK TO SAVEPOINT s1;You need the underlying error
Look earlier in the transaction for the first statement that failed; that is the true cause.
How to avoid it next time
- Handle statement errors in your transaction logic rather than blindly issuing the next statement.
- Use savepoints for optional or retryable steps inside a larger transaction.
Frequently asked questions
Why are all my statements suddenly ignored?
A statement earlier in the transaction failed, so Postgres blocks the rest until you roll back. Look upstream for the first error.
What is a savepoint?
A marker inside a transaction you can roll back to without aborting the whole thing, useful for optional or retryable steps.
Stop struggling with SQL
Use FluentDB, the AI database client for macOS.
Related errors
Part of the PostgreSQL error reference. Last reviewed 2026-07-31.