Keeping the names, in tact, would be helpful. Whatever I change it to, I receive the same error because of the first entry.
I've encoded the csv using Notepad++ to UTF8 and still no luck.
I think "á" followed by the next 2 characters causes the problem. Is there a better encoding for special characters? Is this possible in WIN-1252?
On Thu, Feb 7, 2013 at 10:51 AM, Zach Seaman <znseaman@gmail.com> wrote:
I changed from LATIN1, set my database to UTF8, and my client_encoding is UTF8.
ERROR: invalid byte sequence for encoding "UTF8": 0xe17320
ás[space]
Is it a trial and error type problem now?
On Thu, Feb 7, 2013 at 10:15 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Ken Benson <ken@infowerks.com> writes: > So - the problem may be that /*truly**0x e1 73 71*/ is not a valid UTF-8
> character in the current iteration of PostgreSQL - or at all.
Of course it isn't, which is why Postgres is complaining. Presumably what that data really is is three characters (looks like "ásq") in LATIN1. But Postgres is trying to interpret it in UTF8. As mentioned upthread, the solution is to adjust the client_encoding setting before running the COPY command.
