| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Samuel Smith <pgsql(at)net153(dot)net>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Invalid byte sequence errors on DB restore |
| Date: | 2020-03-16 07:49:18 |
| Message-ID: | c16eddc71bec99ce0fa41c2160b21f59439a18bb.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Björn Lundin | 2020-03-16 08:41:02 | Re: Order by and timestamp |
| Previous Message | Samuel Smith | 2020-03-16 04:18:35 | Invalid byte sequence errors on DB restore |