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.