From: Heikki Linnakangas <hlinnaka@iki.fi>
To: wizard_1024@tut.by
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17501: COPY is failing with "ERROR: invalid byte sequence for encoding "UTF8": 0xe5"
Date: Mon, 30 May 2022 00:09:38 +0300
Message-ID: <6a8f67f2-3baa-1acd-5798-5effe0ce731c@iki.fi> (raw)
In-Reply-To: <196eab40-0754-0fe5-1419-b50459fbb6fc@iki.fi>
References: <17501-128b1dd039362ae6@postgresql.org>
<196eab40-0754-0fe5-1419-b50459fbb6fc@iki.fi>
On 29/05/2022 13:39, Heikki Linnakangas wrote:
> On 28/05/2022 23:52, PG Bug reporting form wrote:
>> The following bug has been logged on the website:
>>
>> Bug reference: 17501
>> Logged by: Vitaly Voronov
>> Email address: wizard_1024@tut.by
>> PostgreSQL version: 14.3
>> Operating system: CentOS Linux release 7.9.2009 (Core)
>> Description:
>>
>> Hello,
>>
>> We've seen a such bug: COPY command shows error "ERROR: invalid byte
>> sequence for encoding "UTF8": 0xe5" on file.
>> The same file with small amount of lines is imported without any errors.
>
> I was able to reproduce this with your instructions. Thank you!
>
> The bug was indeed introduced by commit f82de5c46b, in v14. Attached
> patch fixes it. Barring any objections, I'll commit and backpatch this.
>
> I also noticed that there are some outdated comments in copyfromparse.c
> that still talk about the old protocol version 2 and COPY_OLD_FE. I'll
> clean that up as a separate commit.
Committed. And I included those comment changes in the same commit,
after all.
Thanks for the report!
- Heikki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: hlinnaka@iki.fi, wizard_1024@tut.by, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17501: COPY is failing with "ERROR: invalid byte sequence for encoding "UTF8": 0xe5"
In-Reply-To: <6a8f67f2-3baa-1acd-5798-5effe0ce731c@iki.fi>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox