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

From Albe Laurenz
Subject Re: Bug in UTF8-Validation Code?
Date
Msg-id AFCCBB403D7E7A4581E48F20AF3E5DB201B95600@EXADV1.host.magwien.gv.at
Whole thread Raw
In response to Bug in UTF8-Validation Code?  (Mario Weilguni <mweilguni@sime.com>)
Responses Re: Bug in UTF8-Validation Code?  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Mario Weilguni wrote:
> Is there anything I can do to help with this problem? Maybe
implementing a new
> GUC variable that turns off accepting wrong encoded sequences (so DBAs
still
> can turn it on if they really depend on it)?

I think that this should be done away with unconditionally.
Or does anybody have a good point for allowing corrupt data
in text columns?
Maybe it is the way it is now because nobody could be bothered
to add the appropriate checks...

Yours,
Laurenz Albe


pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Question: pg_class attributes and race conditions ?
Next
From: Andrew Dunstan
Date:
Subject: Re: Bug in UTF8-Validation Code?