On 06/24/2014 06:43 PM, Josh Berkus wrote: >>>> A long idle in transaction state pretty much always indicates a >>>> >>> problematic interaction with postgres. >>> >> >>> >> True. Which makes me wonder whether we shouldn't default this to >>> >> something non-zero -- even if it is 5 or 10 days. > > I'd go for even shorter: 48 hours. I'd suggest 24 hours, but that would > trip up some users who just need really long pg_dumps.
Why would pg_dump be idle for 24 hours? -- Vik -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
