Re: Bug in UTF8-Validation Code?

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
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-18 23:33:21
Message-ID: 87lkhujfem.fsf@stark.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"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);
prosrc
---------------------
abstimein
aclitemin
any_in
anyarray_in
anyelement_in
array_in
bit_in
boolin
box_in
bpcharin
byteain
cash_in
charin
cidin
cidr_in
circle_in
cstring_in
date_in
domain_in
float4in
float8in
inet_in
int2in
int2vectorin
int4in
int8in
internal_in
interval_in
language_handler_in
line_in
lseg_in
macaddr_in
namein
numeric_in
oidin
oidvectorin
opaque_in
path_in
point_in
poly_in
record_in
regclassin
regoperatorin
regoperin
regprocedurein
regprocin
regtypein
reltimein
smgrin
textin
tidin
time_in
timestamp_in
timestamptz_in
timetz_in
tintervalin
trigger_in
unknownin
uuid_in
varbit_in
varcharin
void_in
xidin
xml_in
(64 rows)

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-03-19 00:35:05 Re: Bug in UTF8-Validation Code?
Previous Message Islam Hegazy 2007-03-18 23:09:26 Re: modifying the tbale function