From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Pavel Stehule *EXTERN*" <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: review: CHECK FUNCTION statement |
Date: | 2011-12-15 09:38:55 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C2073C8DD0@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule wrote:
> so removed "quite" option
> and removed multiple check regression tests also - there is missing
> explicit order of function checking, so regress tests can fail :(
There seems to be a problem with the SET clause of CREATE FUNCTION:
ftest=# CREATE OR REPLACE FUNCTION a(integer) RETURNS integer
LANGUAGE plpgsql AS 'BEGIN RETURN 2*$1; END';
CREATE FUNCTION
ftest=# CHECK FUNCTION a(integer);
NOTICE: checked function "a(integer)"
CHECK FUNCTION
ftest=# CREATE OR REPLACE FUNCTION a(integer) RETURNS integer
LANGUAGE plpgsql SET search_path=public AS 'BEGIN RETURN 2*$1; END';
CREATE FUNCTION
ftest=# CHECK FUNCTION a(integer);
The connection to the server was lost. Attempting reset: Failed.
!>
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2011-12-15 11:36:24 | Re: review: CHECK FUNCTION statement |
Previous Message | Hitoshi Harada | 2011-12-15 08:31:39 | Re: JSON for PG 9.2 |