Re: message string fixes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: message string fixes
Date: 2008-01-21 02:48:29
Message-ID: 19410.1200883709@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> It looks to me like RS_isRegis() needs to be tightened up a bit anyway:
> it will accept "^foo" which is valid regex but not valid regis, leading
> to an error being thrown which is not what we want.

I experimented with this and verified that the error could be reached
with a hacked-up affix file.

> If we tighten it to exactly match what RS_compile() will take ... say
> by using the same state-machine logic ... then indeed the ereports
> are internal and can be demoted to elog's. If we make them elogs then
> ISTM they ought to keep saying regis, just so we know where to look
> if they ever do fail ;-)

Patch committed along these lines.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-01-21 02:49:41 Re: message string fixes
Previous Message Tom Lane 2008-01-21 01:52:33 Re: [GENERAL] setof record "out" syntax and returning records