2

I'm working with a PostgreSQL server version 10.5 (can't upgrade it at the moment) running in Docker. XL Deploy is connected to it and I upload a new archive that is 232MB. I get the error FATAL: terminating connection due to idle-in-transaction timeout.

In the config, I saw that idle_in_transaction_session_timeout was set to 11000ms. I updated the value to 600000ms and reload the configuration. I see the message LOG: parameter "idle_in_transaction_session_timeout" changed to "600000" in the logs, so I know the setting has taken.

However, when I upload the archive again, I still get the same FATAL timeout message. It's as if the setting is having no effect.

sffortytwo
  • 127
  • 1
  • 7

1 Answers1

4

As it turns out, the issue was in Postgres, but not in the config file. It seems you can update the value of idle_in_transaction_session_timeout at various levels. In my case, it was at the ROLE level. Issuing this SQL statement fixed the timeout.

ALTER ROLE role_abc SET idle_in_transaction_session_timeout = '10min';
sffortytwo
  • 127
  • 1
  • 7
  • how can you detect this was set on the role level? `pg_dumball --globals-only` comes to mind. – vrms Dec 06 '22 at 10:28