Re: POSIX regex performance bug in 7.3 Vs. 7.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Jon Jensen <jon(at)endpoint(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, wade <wade(at)wavefire(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: POSIX regex performance bug in 7.3 Vs. 7.2
Date: 2003-02-04 22:46:49
Message-ID: 18615.1044398809@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing <hannu(at)tm(dot)ee> writes:
> Tom Lane kirjutas T, 04.02.2003 kell 21:18:
>> What advantages does it have to make it worth considering?

> Should be the same as pcre + support for wide chars.

Well, if someone wants to do the legwork to try it, that interface
should work just about comparably to Spencer's package: I found that
the easiest way to make it work is to use pg_mb2wchar to expand our
internal encoding into an array of pg_wchar's and then apply the
regex package to that form. So as long as sre can handle 4-byte
wide chars it ought to more or less drop in.

I've got a fair amount of cleanup to do on Spencer's package before
I can even think of committing it (ANSIfy function headers, fix comment
formatting so that pg_indent won't completely destroy 'em, etc).
But I'll be glad to send the modified interface file (adt/regexp.c)
to anyone who'd like to try getting it to work with sre.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2003-02-04 22:50:30 Re: POSIX regex performance bug in 7.3 Vs. 7.2
Previous Message Tom Lane 2003-02-04 22:26:15 Re: POSIX regex performance bug in 7.3 Vs. 7.2