From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: missing support of named convention for procedures |
Date: | 2018-03-20 16:31:17 |
Message-ID: | ef1fdaff-22d7-91ca-03c1-4bddec49afc3@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/16/18 06:29, Pavel Stehule wrote:
> attached patch fixes it
The fix doesn't seem to work for LANGUAGE SQL procedures. For example:
CREATE PROCEDURE ptest5(a int, b int DEFAULT 0)
LANGUAGE SQL
AS $$
INSERT INTO cp_test VALUES (a, 'foo');
INSERT INTO cp_test VALUES (b, 'bar');
$$;
CALL ptest5(a => 1, b => 2); -- ok
CALL ptest5(b => 3, a => 4); -- ok
CALL ptest5(5);
ERROR: no value found for parameter 2
CONTEXT: SQL function "ptest5" statement 2
CALL ptest5(a => 6);
ERROR: no value found for parameter 2
CONTEXT: SQL function "ptest5" statement 2
I'm not quite sure why this behaves differently from plpgsql. Needs
more digging.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2018-03-20 16:33:42 | Re: [HACKERS] [PATCH] Incremental sort |
Previous Message | Jeremy Finzel | 2018-03-20 16:19:04 | Re: found xmin from before relfrozenxid on pg_catalog.pg_authid |