Re: Invalid byte sequence errors on DB restore
От
Samuel Smith
Тема
Re: Invalid byte sequence errors on DB restore
Дата
Msg-id
d3b463fe-e974-6ef2-0a1a-f931b5c153bd@net153.net
Ответ на
Re: Invalid byte sequence errors on DB restore (Laurenz Albe)
Список
Дерево обсуждения
Invalid byte sequence errors on DB restore Samuel Smith <pgsql@net153.net>
Re: Invalid byte sequence errors on DB restore Adrian Klaver <adrian.klaver@aklaver.com>
Re: Invalid byte sequence errors on DB restore Samuel Smith <pgsql@net153.net>
Re: Invalid byte sequence errors on DB restore Samuel Smith <pgsql@net153.net>
Re: Invalid byte sequence errors on DB restore Laurenz Albe <laurenz.albe@cybertec.at>
Re: Invalid byte sequence errors on DB restore Samuel Smith <pgsql@net153.net>
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 errors: >> >> invalid byte sequence for encoding "UTF8": 0xa0 >> and >> invalid byte sequence for encoding "UTF8": 0xd7 0x20 >> >> >> This is on a pg 9.2.24 instance. Any tips to troubleshoot? > > Simple. Fix the offending string and upgrade. > > Failure to enforce correct encoding is a bug in PostgreSQL, and a > number of such bugs have been fixed over the decades, so you might > be happier with a less ancient version. > > Yours, > Laurenz Albe > Yes I thought I had seen some info on bug fixes in newer versions. I will pass this on to the system admins/stakeholders. Thanks, Samuel Smith
В списке pgsql-general по дате отправления