Re: copy command PANIC in --encoding='utf8' createdb option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sil Lee <leesil(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: copy command PANIC in --encoding='utf8' createdb option
Date: 2004-10-29 19:20:10
Message-ID: 19569.1099077610@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Sil Lee <leesil(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-10-29 19:22:01 Re: PostgreSQL 8.0 Beta 4 - Qualified ORDER BY column name not working on UNION query
Previous Message Stephan Szabo 2004-10-29 18:33:16 Re: Insertion Deferrable