From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: message string fixes |
Date: | 2008-01-20 23:27:55 |
Message-ID: | 14842.1200871675@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Teodor Sigaev wrote:
>> Hmm. If regis detects an error in expression then it will be an error for
>> regex library too. At least, it was supposed to be.
> And those that are not, probably are not what the user intends anyway,
> with the pattern language being so narrow.
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.
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 ;-)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-01-20 23:41:03 | Re: Friendly help for psql |
Previous Message | Tom Lane | 2008-01-20 23:22:52 | Re: Minor bug in src/port/rint.c |