I feel dumb asking this question, but I can't seem to find the answer online.
I'm running serializable transactions, and so naturally, they will sometimes fail with the error "could not serialize access due to concurrent update." But then I try to issue a ROLLBACK so I can continue using the connection, and I get error 25P02: "current transaction is aborted, commands ignored until end of transaction block." ...doesn't "ROLLBACK" end a transaction block? What does Postgres want here? How can I retry without closing the connection altogether? --Brian -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
