| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Jeff Davis <pgsql(at)j-davis(dot)com>, Michael Fuhr <mike(at)fuhr(dot)org>, Mario Weilguni <mweilguni(at)sime(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Albe Laurenz <all(at)adv(dot)magwien(dot)gv(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bug in UTF8-Validation Code? |
| Date: | 2007-03-19 00:35:05 |
| Message-ID: | 45FDDAB9.6060009@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gregory Stark wrote:
> "Andrew Dunstan" <andrew(at)dunslane(dot)net> writes:
>
>
>> Below is a list of the input routines in the adt directory, courtesy of grep.
>>
>
> Grep isn't a good way to get these, your list missed a bunch.
>
> postgres=# select distinct prosrc from pg_proc where oid in (select typinput from pg_type);
>
>
[snip]
> (64 rows)
>
>
Ok, good point. Now, which of those need to have a check for valid encoding?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-03-19 03:22:13 | Re: Buildfarm feature request: some way to track/classify failures |
| Previous Message | Gregory Stark | 2007-03-18 23:33:21 | Re: Bug in UTF8-Validation Code? |