Re: Bug in UTF8-Validation Code?

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql(at)markdilger(dot)com, kleptog(at)svana(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bug in UTF8-Validation Code?
Date: 2007-04-02 04:49:58
Message-ID: 20070402.134958.58463924.t-ishii@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Mark Dilger <pgsql(at)markdilger(dot)com> writes:
> > Refactoring the way these table driven functions work would impact
> > lots of other code. Just grep for all files #including mb/pg_wchar.h
> > for the list of them. The list includes interfaces/libpq, and I'm
> > wondering if software that links against postgres might rely on these
> > function prototypes?
>
> No, we've never exported those with the intent that client code should
> use 'em. Doing so would require importing non-public headers, and
> anyone who does that can have no grounds for complaining if the headers
> change incompatibly.

I thought PQescapeString() of 8.3 uses mbverify functions to make sure
that user supplied multibyte string is valid.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ITAGAKI Takahiro 2007-04-02 04:56:04 UTF8MatchText
Previous Message Tom Lane 2007-04-02 04:32:52 Re: Bug in UTF8-Validation Code?