Re: Bug in UTF8-Validation Code? - Mailing list pgsql-hackers

From Mario Weilguni
Subject Re: Bug in UTF8-Validation Code?
Date
Msg-id 200703131455.45209.mweilguni@sime.com
Whole thread Raw
In response to Re: Bug in UTF8-Validation Code?  ("Albe Laurenz" <all@adv.magwien.gv.at>)
Responses Re: Bug in UTF8-Validation Code?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Am Dienstag, 13. März 2007 14:46 schrieb Albe Laurenz:
> Mario Weilguni wrote:
> > Steps to reproduce:
> > create database testdb with encoding='UTF8';
> > \c testdb
> > create table test(x text);
> > insert into test values ('\244'); ==> Is akzepted, even if not UTF8.
>
> This is working as expected, see the remark in
> http://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQ
> L-SYNTAX-STRINGS
>
> "It is your responsibility that the byte sequences you create
>  are valid characters in the server character set encoding."

In that case, pg_dump is doing wrong here and should quote the output. IMO it
cannot be defined as working as expected, when this makes any database dumps
worthless, without any warnings at dump-time.

pg_dump should output \244 itself in that case.

Best regards,Mario Weilguni


pgsql-hackers by date:

Previous
From: "Albe Laurenz"
Date:
Subject: Re: Bug in UTF8-Validation Code?
Next
From: David Fetter
Date:
Subject: Re: My honours project - databases using dynamically attached entity-properties