Monitoring for long running transactions

From: Samuel Smith <pgsql(at)net153(dot)net>
To: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Monitoring for long running transactions
Date: 2020-06-04 17:00:04
Message-ID: d2f5ded1-7820-e25f-2477-403283fbb2d0@net153.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We had a customer complaining of random data loss for the last 6 months
or so. We eventually tracked it down to a combination of bad coding and
a couple of bugs with the ORM. Basically, 'BEGIN' was being emitted by
the web app when viewing a certain page and 'COMMIT' was never emitted
after that. So once the app would get restarted, all data changes would
be lost. Definitely worst case scenario.

So the question is, what is the best way to monitor for this scenario
going forward? Are there any plugins or community recommended scripts
already made?

Regards,

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Paul van der Linden 2020-06-04 17:04:54 Possible improvement
Previous Message Susan Joseph 2020-06-04 16:50:58 Re: PostgreSQL 11 with SSL on Linux