> On Nov 7, 2017, at 12:16 AM, Thomas Kellerer <spam_eater@xxxxxxx> wrote: > > Rob Sargent schrieb am 06.11.2017 um 23:09: >> Gosh I wish I could learn to proof-read my posts. >> My support crew graciously set >> >> idle_transaction_timeout = 1 >> >> Now to ponder if I need zero or some large number. > > The unit of that setting is milliseconds (if no unit is specified). > zero disables that feature. > > One millisecond seems like an awfully short period to allow a transaction to be idle. > > I would figure values in "minutes" to be more realistic depending on the workload and characteristics of the application. > > A transaction that has several seconds of "think time" between individual statements doesn't seem that unrealistic. > > > Thomas > I see I didn’t clarify that the timeout was set in the pgbouncer configuration. (I had shown upstream that it was NOT set for the postgres server.) In pgbouncer, the unit is seconds. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general