| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Marko Kreen" <markokr(at)gmail(dot)com> |
| Cc: | "Jonathan Gray" <jon5pg(at)streamy(dot)com>, pgsql-hackers(at)postgresql(dot)org, dmitry(at)taurussoft(dot)org |
| Subject: | Re: Pl/pgsql functions causing crashes in 8.2.2 |
| Date: | 2007-02-06 15:21:45 |
| Message-ID: | 9563.1170775305@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Marko Kreen" <markokr(at)gmail(dot)com> writes:
> On 2/6/07, Marko Kreen <markokr(at)gmail(dot)com> wrote:
>> STRICT IMMUTABLE fixed the crash for me so seems it was bug
>> in the module. Although it did not happen in 8.2.1 so seems
>> some change in 8.2.2 made it trigger.
> Trigger was following patch:
> http://archives.postgresql.org/pgsql-committers/2007-02/msg00016.php
> as function test.break_guid() assigns NULLs to gplus_ret.
So in fact the problem was that the input function was not declared
STRICT and yet failed to handle nulls... which means it was broken
as of 8.2.0, the OP just hadn't tried to throw a null at it except
in the context of plpgsql ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-02-06 16:06:11 | Re: Dead code in _bt_split? |
| Previous Message | Andrew Sullivan | 2007-02-06 15:20:44 | Re: Modifying and solidifying contrib |