Re: Error on failed COMMIT

Vladimir Sitnikov <sitnikov.vladimir@gmail.com>

From: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Vik Fearing <vik@postgresfriends.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Dave Cramer <davecramer@gmail.com>
Date: 2020-02-25T08:42:47Z
Lists: pgsql-hackers
Tom>I think we still end up concluding that altering this behavior has more
Tom>downside than upside.

What is the downside?

Applications, drivers, and poolers already expect that commit might produce
an error and terminate the transaction at the same time.

"The data is successfully committed to the database if and only if commit
returns without error".
^^^ the above is way easier to reason about than "user must check multiple
unrelated outcomes to tell if the changes are committed or not".

Vladimir