This worked for me - thank you so much! The SELECT did fail.
Also I cannot reproduce a scenario when "applications must not depend on
results read during a transaction that later aborted;". In this example the
SELECT itself has failed.
Can you show an example where a SELECT completes, but the COMMIT blows up?
View this message in context:
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: