From: | Geoffrey Myers <lists(at)serioustechnology(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: error messages during restore |
Date: | 2011-03-22 17:28:51 |
Message-ID: | 4D88DC53.9060305@serioustechnology.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Geoffrey Myers <lists(at)serioustechnology(dot)com> writes:
>> So we are in the process of converting our databases from SQL_ASCII to
>> UTF8. If a particular row won't import because of the encoding issue we
>> get an error like:
>
>> pg_restore: [archiver (db)] Error from TOC entry 5317; 0 1266711 TABLE
>> DATA logs postgres
>> pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence
>> for encoding "UTF8": 0x90
>> HINT: This error can also happen if the byte sequence does not match
>> the encoding expected by the server, which is controlled by
>> "client_encoding".
>> CONTEXT: COPY logs, line 590744
>
>> Question is, it would be really nice if we could figure out the actual
>> column name in that table.
>
> Sorry, no chance of that. The line is converted to server encoding
> before any attempt is made to split it into columns. Since the column
> delimiter is potentially encoding-specific, there's not really any
> alternative to doing it that way.
>
> regards, tom lane
Thanks for the follow up Tom.
--
Until later, Geoffrey
"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson
From | Date | Subject | |
---|---|---|---|
Next Message | Viliam Ďurina | 2011-03-22 19:05:28 | Re: share directory on windows |
Previous Message | Adrian Schreyer | 2011-03-22 16:57:31 | Re: Weird problems with C extension and bytea as input type |