On 06/26/2014 06:45 AM, Fujii Masao wrote: >> The point of this feature, AFAICS, is to detect clients that are failing >> > to issue another query or close their transaction as a result of bad >> > client logic. It's not to protect against network glitches. > > If so, the document should explain that cleanly. Otherwise users may > misunderstand this parameter and try to use it to protect even long > transaction > generated by network glitches or client freeze.
What does pg_stat_activity say for those cases? If it's able to say "idle in transaction", then this patch covers it. If it isn't, then that seems like a different patch. -- Vik -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
