Another plpgsql crash
(bs@niggard.org) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Another plpgsql crash
Long Description
Ok, just found another one:
The function crashes, when the corresponding user is not found.
This one just looks too common, so i guess i messed up installation?
Sample Code
CREATE FUNCTION "new_news" (varchar ) RETURNS int4 AS '
DECLARE
letzte_nachricht_p INT4;
BEGIN
SELECT letzte_nachricht INTO letzte_nachricht_p FROM luser WHERE uid = $1;
END;
' LANGUAGE 'plpgsql';
No file was uploaded with this report
See reply to your previous bug report. 7.1 doesn't have this problem or fetch
the latest from CVS's REL7_1_STABLE branch.
Show quoted text
On Wed, May 09, 2001 at 09:15:16AM -0400, pgsql-bugs@postgresql.org wrote:
(bs@niggard.org) reports a bug with a severity of 2
The lower the number the more severe it is.Short Description
Another plpgsql crashLong Description
Ok, just found another one:
The function crashes, when the corresponding user is not found.This one just looks too common, so i guess i messed up installation?
Sample Code
CREATE FUNCTION "new_news" (varchar ) RETURNS int4 AS '
DECLARE
letzte_nachricht_p INT4;
BEGIN
SELECT letzte_nachricht INTO letzte_nachricht_p FROM luser WHERE uid = $1;
END;
' LANGUAGE 'plpgsql';No file was uploaded with this report
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
pgsql-bugs@postgresql.org writes:
The function crashes, when the corresponding user is not found.
If this is 7.1.1, then that's an already-known problem (I broke
plpgsql's SELECT for the case of no rows found :-(). It'll be
fixed in 7.1.2, or you can get the source-code patch from
techdocs.postgresql.org.
regards, tom lane