Re: invalidly encoded strings

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: invalidly encoded strings
Date: 2007-09-09 10:59:45
Message-ID: 20070909105945.GA11896@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Sun, Sep 09, 2007 at 12:02:28AM -0400, Andrew Dunstan wrote:
> . what do we need to do to make the verification code more efficient? I
> think we need to address the correctness issue first, but doing so
> should certainly make us want to improve the verification code. For
> example, I'm wondering if it might benefit from having a tiny cache.

It has been pointed out the the verification for UTF-8 is very
inefficient, involving several function calls to first get the length,
then check characters, etc. It could be significantly improved. I don't
know whether a cache would make any useful difference.

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-09 11:46:19 Re: invalidly encoded strings
Previous Message Heikki Linnakangas 2007-09-09 09:22:07 Re: ispell dictionary broken in CVS HEAD ?

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2007-09-09 11:46:19 Re: invalidly encoded strings
Previous Message Simon Riggs 2007-09-09 08:16:47 Re: HOT patch - version 15