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"
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions