Postgres Pro
Downloads
Home   >   mailing lists

Re: copy command PANIC in --encoding='utf8' createdb option - Mailing list pgsql-bugs

From Tom Lane
Subject Re: copy command PANIC in --encoding='utf8' createdb option
Date
Msg-id 19569.1099077610@sss.pgh.pa.us
Whole thread Raw
In response to copy command PANIC in --encoding='utf8' createdb option  (Sil Lee <leesil@gmail.com>)
List pgsql-bugs
Tree view 
Sil Lee <leesil@gmail.com> writes:
> test1=> \copy t1 (col1) from '/opt/lgsec/dmp/test.dmp'
> \.
> PANIC:  ERRORDATA_STACK_SIZE exceeded
> test1=>

> ^^; postmaster log
> WARNING:  ignoring unconvertible UHC character 0xb85f
> CONTEXT:  COPY t1, line 1: "/system/workbin/등락종??.TXT.20040319"
> WARNING:  ignoring unconvertible UTF-8 character 0xeeb6f4
> CONTEXT:  COPY t1, line 1: "/system/workbin/등락종??.TXT.20040319"
> WARNING:  ignoring unconvertible UTF-8 character 0xeeb6f4

Good catch.  It's trying to reverse-convert the COPY data line from server
encoding back to client encoding, which would be fine except the line is
still in client encoding :-(.  I think we'll have to skip providing the
actual data line contents in this scenario.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: Insertion Deferrable
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL 8.0 Beta 4 - Qualified ORDER BY column name not working on UNION query