From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Dmitriy <im(at)ionflux(dot)ru>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3841: core dump in uuid-ossp |
Date: | 2007-12-27 20:42:26 |
Message-ID: | 20211.1198788146@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> Can we throw some more specific SQLSTATE than the default "internal
>> error" here?
> Hmm. I looked at the extant list, and found that the contrib/xml2 code
> uses ERRCODE_EXTERNAL_ROUTINE_EXCEPTION whereas pgcrypto uses
> ERRCODE_EXTERNAL_ROUTINE_INVOCATION_EXCEPTION.
Either of those would be fine with me; it's not totally clear what
distinction the SQL spec intends to draw. The best I can divine is that
the latter is for bad arguments to the external routine, but we can't
really tell whether that's applicable.
> (Sorry, totally unrelated:) Wow, in plpython.c there is this:
> ...
> I wonder why is it a good idea to have this report be FATAL.
Yeah, I noticed that recently and was annoyed by it, but I'm not sure
how safe it is to change. I suspect the author was worried about leaked
memory in event of a failure.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2007-12-27 21:25:30 | Re: BUG #3822: Nonstandard precedence for comparison operators |
Previous Message | Simon Riggs | 2007-12-27 20:20:01 | Re: BUG #3843: archiver process is restarted after the smart shutdown |