error: current transaction is aborted commands ignored until end of transaction block

Error: Current Transaction Is Aborted Commands Ignored Until End Of Transaction Block Code Had Ignored
Error: Current Transaction Is Aborted Commands Ignored Until End Of Transaction Block Driver Is Not

Thought it should be something stupid, because I didnt really try to do anything that complicated.

ERROR: current transaction is aborted, commands ignored until end of.

ERROR: current transaction is aborted, commands ignored until end of transaction block.

STATEMENT: CREATE TABLE ISPNMIXEDBINARYTABLEconfigCache(IDCOLUMN VARCHAR(255) NOT NULL, DATACOLUMN BYTEA, TIMESTAMPCOLUMN BIGINT, PRIMARY KEY (IDCOLUMN)).

ERROR: relation ispnmixedbinarytableconfigcache does not exist at character 22.

Finally it was due to our (nice) Logback usage fed with a toString() -overloaded DAO object that caused the error and was nicely swallowed (but accidentially unnoticed by me): log.info( bla bla:, obj ) produced bla bla: FAILED toString().

But that wasnt enough, THEN you used that same connection, using the SAME TRANSACTION to run another query.

The exception gets thrown on the second, correctly formed query because you are using a broken transaction to do additional work.

It works because then the failed SQL is just ignored as a failed SQL statement.

You are welcome to fail SQL statements all you want and PostgreSQL wont stop you.

Oracle was making you soft in the middle letting you do dumb stuff and overlooking it.

Why isnt there an option like the first to make it behave like Oracle but without the auto-commit.

If you need to issue multiple updates, and one failure should not stop subsequent updates, simply call rollback() on the Connection when an SQLException is caught.

Anyway I realized this is in-line with the PostgreSQL philosophy of forcing the user to make everything explicit, whereas Oracle has the philosophy of implicitly taking care of a lot of things.

This can also be reproduced directly with psql.

If this issue is triggered by a constraint violation, the PostgreSQL devs recommend checking for a conflict ahead of time (query before updateinsert) or using savepoints to roll back to the point before the updateinsert.

Error: Current Transaction Is Aborted Commands Ignored Until End Of Transaction Block Code Had Ignored

This typically means that database threw an exception that your code had ignored and now expecting next queries to return some data.

Maybe check if theres a newer version of the library youre using or rise the issue within their bug tracker.

If youll find the exact SQL that caused the issue, youll have some field to eliminate the issue using PostgreSQL extensibility.

Error: Current Transaction Is Aborted Commands Ignored Until End Of Transaction Block Driver Is Not

Perhaps the Postgres driver is not throwing one of the expected exceptions.

Perhaps it is the JdbcUtil.safeClose() statements that are not doing their job.

Works for me also in environment of PHP, Doctrine2 and Postgres (9.5).

Thanks.

Overhead due to handling a savepoint around the statement execution is kept very low (see link above for details).