Samuel Smith schrieb am 04.06.2020 um 21:59:
Sorry, I should have clarified that I was aware of the
pg_stat_activity table. That is how we found the problem in the first
place. And yes I could just write a bash script and run it in cron. I
just didn't know if there was a more "official" way to go
## Samuel Smith (pg...@net153.net):
> Sorry, I should have clarified that I was aware of the pg_stat_activity
> table. That is how we found the problem in the first place. And yes I
> could just write a bash script and run it in cron. I just didn't know if
> there was a more "official" way to g
On 6/4/20 12:59 PM, Samuel Smith wrote:
On 6/4/20 2:29 PM, Adrian Klaver wrote:
Sorry, I should have clarified that I was aware of the pg_stat_activity
table. That is how we found the problem in the first place. And yes I
could just write a bash script and run it in cron. I just didn't k
On 6/4/20 2:29 PM, Adrian Klaver wrote:
On 6/4/20 10:00 AM, Samuel Smith wrote:
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
On 6/4/20 10:00 AM, Samuel Smith wrote:
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
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 tha
