| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at> |
| Cc: | Mario Weilguni *EXTERN* <mweilguni(at)sime(dot)com>, Michael Paesold <mpaesold(at)gmx(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug in UTF8-Validation Code? |
| Date: | 2007-03-16 13:06:08 |
| Message-ID: | 45FA9640.6090201@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Albe Laurenz wrote:
> 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...
>
>
I agree. It's more or less an integrity violation, IMNSHO.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2007-03-16 13:37:13 | Re: tsearch_core for inclusion |
| Previous Message | Jan Wieck | 2007-03-16 13:03:37 | Re: As proposed the complete changes to pg_trigger and pg_rewrite |