Stefan Sassenberg wrote:
Hello,
I've got a failing sql-Script that I execute with the psql command. The
Script contains:
----------------------------8<-----------------------------
SET CLIENT_ENCODING = 'LATIN1';
<snip>
The database that script is applied to is UTF8 encoded.
Stefan Sassenberg wrote:
> As I see it, ERRORDATA_STACK_SIZE is a constant that is defined in the
> code (pgsql/src/backend/utils/error/elog.c) as 5. 5 illegal bytecodes
> that postgresql finds in my statement are enough to cause the panic.
Could the difference between CLIENT_ENCODING = 'LATIN1' and
database_encoding = UTF8 create the illegal bytecodes?
I just found a way to get a similar error -
create db with utf8 encoding
save file with the create table command - save as unicode-utf16
I then get -
%>psql enctest < test
ERROR: invalid byte sequence for encoding "UTF8": 0xfe
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".
If I save the file as latin1 or utf8 I have no problems.
I would be looking for the error somewhere in the (some other
statements) part and would expect an invisible/unprintable char of some
sort.
SET CLIENT_ENCODING = 'LATIN1';
(Some other statements)
CREATE TABLE
--
Shane Ambler
[EMAIL PROTECTED]
Get Sheeky @ http://Sheeky.Biz
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
