On Tue, Sep 6, 2011 at 12:48 PM, Bruce Momjian <bruce@momjian.us> wrote:
> Josh Berkus wrote:
>> I have another example of this issue with WIN1252. =A0This line in a copy
>> file:
>>
>> 659446 =A0828 =A0 =A0 1 =A0 =A0 =A0 /6???\bH@^W^Za$H???\b???@\\/ =A0 =A0=
<p><p></p><p>No
>> valid or unique HTTP objects found in XML response.</p></p>
>>
>> Into this table:
>>
>> =A0 =A0 =A0Table "public.ep_tests"
>> Column =A0| =A0 =A0 Type =A0 =A0 | Modifiers
>> ---------+--------------+-----------
>> id =A0 =A0 =A0| bigint =A0 =A0 =A0 | not null
>> v_id =A0 =A0| integer =A0 =A0 =A0| not null
>> status =A0| character(1) | not null
>> vkey =A0 =A0| text =A0 =A0 =A0 =A0 |
>> details | text =A0 =A0 =A0 =A0 |
>>
>> Results in this error while loading the data:
>>
>> the following error is encounted by the \copy: ERROR: =A0missing data for
>> column "details"
>> CONTEXT: =A0COPY ep_tests, line 1028752: "659446 =A0828 =A0 =A0 1 =A0 =
=A0 =A0 /6???\bH@?"
>>
>> The dump file was produced by using 9.0.3's pg_dump in text mode to dump
>> an 8.2 database, then using 9.0.3's psql to load the file. =A0Both serve=
rs
>> are UTF8, locale WIN1252.
>>
>> So it looks like we're not successfully escaping characters on WIN1252.
>> =A0The characters in question are also latin characters.
>>
>> We've reproduced this on a clean install.
>
> Has this been fixed?
I don't think so. It's not really clear to me what the issue is. Is
there some confusion between the encoding of the file and the encoding
in use in the client session? It's odd that we would have a bug that
only affects win1252.
--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company