On Tue, Feb 25, 2020 at 12:47 PM Vladimir Sitnikov <sitnikov.vladi...@gmail.com> wrote: > Noone suggested that "commit leaves the session in a transaction state". > Of course, every commit should terminate the transaction. > However, if a commit fails (for any reason), it should produce the relevant > ERROR that explains what went wrong rather than silently doing a rollback.
OK, I guess I misinterpreted the proposal. That would be much less problematic -- any driver or application that can't handle ERROR in response to an attempted COMMIT would be broken already. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
