Skip to Main Content
Status Not under consideration
Workspace * IBM Cloud Ideas
Categories Databases
Created by Guest
Created on Apr 30, 2021

Make `idle_in_transaction_session_timeout` a configurable setting in databases for postgres

Real life scenario

  1. application has a bug that causes a DB transaction to never be closed

  2. postgres needs to keep old tuple versions for as long the transction is open

  3. autovaccum can't delete old tuples

  4. tables start to get bloated

  5. performance degrades


This could be mitigated by setting idle_in_transaction_session_timeout to a reasonable value (e.g., 4h - value obviously depends on specific workloads), however that setting is not currently configurable in "Databases for Postgres"

Idea priority Medium
  • Guest
    May 31, 2022

    This can already set this on a per database or per user basis. it will persist and survive backup and restore. We believe this is sufficient to solve the user problem outlined. Please let us know if you disagree and we can re-evaluate.