Invalid byte sequence errors on DB restore

2020-03-15 Thread Samuel Smith
r encoding "UTF8": 0xd7 0x20 This is on a pg 9.2.24 instance. Any tips to troubleshoot? Regards, Samuel Smith

Re: Invalid byte sequence errors on DB restore

2020-03-16 Thread Samuel Smith
On 3/16/20 2:49 AM, Laurenz Albe wrote: On Sun, 2020-03-15 at 23:18 -0500, Samuel Smith wrote: My current DB backup routine is just to call pg_dump and pipe to gzip. We recently started to get a failure to restore (which is basically just using psql -f on the pg_dump file) with the following

Re: Invalid byte sequence errors on DB restore

2020-03-16 Thread Samuel Smith
On 3/16/20 9:33 AM, Adrian Klaver wrote: On 3/15/20 9:18 PM, Samuel Smith wrote: My current DB backup routine is just to call pg_dump and pipe to gzip. We recently started to get a failure to restore (which is basically just using psql -f on the pg_dump file) with the following errors

Re: Invalid byte sequence errors on DB restore

2020-03-19 Thread Samuel Smith
On 3/15/20 11:18 PM, Samuel Smith wrote: My current DB backup routine is just to call pg_dump and pipe to gzip. We recently started to get a failure to restore (which is basically just using psql -f on the pg_dump file) with the following errors: invalid byte sequence for encoding "

Monitoring for long running transactions

2020-06-04 Thread Samuel Smith
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

Re: Monitoring for long running transactions

2020-06-04 Thread Samuel Smith
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 bein