Re: procedures and plpgsql PERFORM

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: procedures and plpgsql PERFORM
Date: 2017-12-14 14:38:39
Message-ID: 10998.1513262319@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> writes:
> We allow a function to be invoked as part of PERFORM statement in plpgsql
> ...
> But we do not allow a procedure to be invoked this way

> Procedures fit that category and like functions, I think, we should
> allow them be invoked directly without any quoting and CALL
> decoration.

How is that going to work? What if the procedure tries to commit the
current transaction?

IOW, this is not merely a syntactic-sugar question.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2017-12-14 14:49:26 Re: [HACKERS] pgbench more operators & functions
Previous Message Teodor Sigaev 2017-12-14 13:26:48 Re: [HACKERS] pgbench more operators & functions