copy from .. How to get rid of encoding check for bytea coumns

From: "Roman Golis" <rgolis(at)aps-holding(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: copy from .. How to get rid of encoding check for bytea coumns
Date: 2012-09-09 01:55:20
Message-ID: 20120909015520.795a7a0d@mail.aps-cz.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I am trying to load data into a rather simple table:

CREATE TABLE "public"."files" (
"id" SERIAL,
"idchar" CHAR(32) NOT NULL,
"content" BYTEA,
CONSTRAINT "files_pkey" PRIMARY KEY("id")
) WITHOUT OIDS;

with this command:

copy files (idchar, content) from '/data/1.dat' delimiter '|';

The database encoding is UTF-8.

Here is an example of the data file content:

0C2CCE6941194369B020000B616F1301|\xFF\xD8\xFF\xE0\x00\x10\x4A\x46\x49\x46\x00\x01

And I get this error:

ERROR: invalid byte sequence for encoding "UTF8": 0xff

The command

set client_encoding = 'SQL_ASCII';

Does not helps at all, the result is the same error message.

How can I turn off that annoying codepage checking during COPY FROM ?

Isn't it a bug ?

In my humble opinion, tt definitely should not check the encoding for columns of type bytea.

Cheers, R.G.

Disclaimer: http://www.aps-holding.com/disclaimer.html

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Herouth Maoz 2012-09-09 09:25:03 Index creation takes more time?
Previous Message Bret Stern 2012-09-08 20:18:25 Re: Add a check an a array column