Re: missing support of named convention for procedures - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: missing support of named convention for procedures
Date
Msg-id CAFj8pRCmXvOKpA6Wn7_k=YwdTn4gi2B5npSvU6x_fkzaPx7Sdw@mail.gmail.com
Whole thread Raw
In response to Re: missing support of named convention for procedures  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: missing support of named convention for procedures  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: missing support of named convention for procedures  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers


2018-03-16 8:43 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:


2018-03-15 22:13 GMT+01:00 Pavel Stehule <pavel.stehule@gmail.com>:
Hi

create or replace procedure proc2(in a int, in b int)
as $$
begin
  a := a * 10;
  b := b * 10;
end;
$$ language plpgsql;

postgres=# call proc2(a => 10,b => 20);
ERROR:  XX000: unrecognized node type: 107
LOCATION:  ExecInitExprRec, execExpr.c:2114

Defaults are not supported too:

 postgres=# create or replace procedure foo1(a int, b int, c int default 10)
as $$
begin
  raise notice 'a: %, b: %, c: %', a, b, c;
end;
$$ language plpgsql;
CREATE PROCEDURE
postgres=# call foo1(10,20);
NOTICE:  00000: a: 10, b: 20, c: -778600432
LOCATION:  exec_stmt_raise, pl_exec.c:3643
CALL

attached patch fixes it

Regards

Pavel
 


Regards

Pavel


Attachment

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] why not parallel seq scan for slow functions
Next
From: Pavel Stehule
Date:
Subject: Re: missing support of named convention for procedures