On 11/2/15 11:15 AM, Pavel Stehule wrote:
I have not strong idea about how to solve it well - maybe introduce transaction_idle_timeout and session_idle_timeout?
Yes, please. This is a very common problem. I would love a better way to detect (or prevent) clients from being brain-dead about how they're using transactions, but short of that this is the next best thing.
Actually, one other thing that would help is to have the ability to turn this into an ERROR:
begin; WARNING: there is already a transaction in progress -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
