Search Postgresql Archives
Monitoring for long running transactions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Monitoring for long running transactions
- From: Samuel Smith <pgsql@xxxxxxxxxx>
- Date: Thu, 4 Jun 2020 12:00:04 -0500
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
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,
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]