Skip to Main Content
IBM Cloud - Structured Ideas

This portal is to open public enhancement requests against IBM Cloud and its products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

IBM Cloud Support Center ( – Use this site for any IBM Cloud defect or support need.

Stack Overflow ( – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud". - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
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
  • Admin
    James Bennett
    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.