e to handle the pressure, slowing down the overall database performance, the report said."
>
> Again, pretty much content-free. For all you know some application was creating savepoints, needlessly:
>
> https://www.postgresql.org/docs/10/static/sql-savepoint.html
>
> and not cleaning up after itself.
>
> The content is here:
>
> "Following the Prime Day outage, Amazon engineers filled out a 25-page report, which Amazon calls a correction of
error.It's a standard process that Amazon uses to try to understand why a major incident took place and how to keep it
fromhappening in the future."
>
> Not sure if that is publicly available or not, though my hunch is no.
I think PG gurus in this list can expand on the clue as to what could have gone wrong with savepoints in PG under heavy
load.