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:
http://postgresql.1045698.n5.nabble.com/How-to-reproduce-serialization-failure-for-a-read-only-transaction-tp5785569p5785618.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.