Re: BUG #5944: COPY FROM doesn't work with international characters - Mailing list pgsql-bugs

From Josh Berkus
Subject Re: BUG #5944: COPY FROM doesn't work with international characters
Date
Msg-id 4D8B9332.80308@agliodbs.com
Whole thread Raw
In response to BUG #5944: COPY FROM doesn't work with international characters  ("Nathan Davalos" <n.davalos@sharedmarketing.com>)
Responses Re: BUG #5944: COPY FROM doesn't work with international characters  (Bruce Momjian <bruce@momjian.us>)
List pgsql-bugs
I have another example of this issue with WIN1252.  This line in a copy
file:

659446  828     1       /6�\bH@^W^Za$H�\b�@\\/    <p><p></p><p>No
valid or unique HTTP objects found in XML response.</p></p>

Into this table:

     Table "public.ep_tests"
Column  |     Type     | Modifiers
---------+--------------+-----------
id      | bigint       | not null
v_id    | integer      | not null
status  | character(1) | not null
vkey    | text         |
details | text         |

Results in this error while loading the data:

the following error is encounted by the \copy: ERROR:  missing data for
column "details"
CONTEXT:  COPY ep_tests, line 1028752: "659446  828     1       /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.  Both servers
are UTF8, locale WIN1252.

So it looks like we're not successfully escaping characters on WIN1252.
 The characters in question are also latin characters.

We've reproduced this on a clean install.


--
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com

pgsql-bugs by date:

Previous
From: Kasia Tuszynska
Date:
Subject: Re: ERROR: character 0xe3809c of encoding "UTF8" has no equivalent in EUC_JP
Next
From: Kris Jurka
Date:
Subject: Re: BUG #5943: jdbc client doesn't omit pg_toast_temp tables from schema views