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:
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you.
To post a new idea - select "Add a new idea" and where asked select the appropriate category this idea relates to. Provide requested information to allow us to get a better understanding of your request.
Vote ideas that matter most to you.
Get feedback from the IBM team to refine your idea.
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
The shorter URL for this site: http://ibm.biz/cloudideas
For any defect or support needs, visit the IBM Cloud Support Center.
For technical Q&A, use Stack Overflow and tag with "ibm-cloud".
Real life scenario
application has a bug that causes a DB transaction to never be closed
postgres needs to keep old tuple versions for as long the transction is open
autovaccum can't delete old tuples
tables start to get bloated
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 |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
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.