Re: Stored procedures and out parameters

From: Andres Freund <andres(at)anarazel(dot)de>
To: Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
Cc: Shay Rojansky <roji(at)roji(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, daniel(at)manitou-mail(dot)org, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Stored procedures and out parameters
Date: 2018-08-16 17:14:16
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2018-08-16 20:08:20 +0300, Vladimir Sitnikov wrote:
> Shay>On the other hand, releasing *without* this also has its consequence,
> namely setting in stone that the database-independent language API cannot
> be used for invoking the new stored procedures
> Shay>So I hope you at least consider going through the thought process
> about allowing this.
> +1
> I wonder if "CALL ..." can be excluded from PostgreSQL 11 release.
> It is really important feature for the release?

Are you actually suggesting we effectively drop procedure soupport?


Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-08-16 17:26:46 Re: Memory leak with CALL to Procedure with COMMIT.
Previous Message Marina Polyakova 2018-08-16 17:12:50 Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors