Re: Bug in UTF8-Validation Code?

From: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>
To: "Mario Weilguni *EXTERN*" <mweilguni(at)sime(dot)com>, "Michael Paesold" <mpaesold(at)gmx(dot)at>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in UTF8-Validation Code?
Date: 2007-03-16 12:25:06
Message-ID: AFCCBB403D7E7A4581E48F20AF3E5DB201B95600@EXADV1.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2007-03-16 13:03:37 Re: As proposed the complete changes to pg_trigger and pg_rewrite
Previous Message Pavan Deolasee 2007-03-16 11:50:05 Question: pg_class attributes and race conditions ?