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
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"
Do not place IBM confidential, company confidential, or personal information into any field.