Date: Sat, 13 Oct 2018 21:01:57 -0400
From: Bruce Momjian <bruce@momjian.us>
To: fn ln <emuser20140816@gmail.com>
Cc: pgsql-docs@postgresql.org
Subject: Re: v11: RETURN syntax for procedure
Message-ID: <20181014010157.GB25796@momjian.us>
References: 
 <CA+99BHqk-zAWA_qByg_P1TjQ8v5LCFQT4e7r5uke0eOQLe955g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CA+99BHqk-zAWA_qByg_P1TjQ8v5LCFQT4e7r5uke0eOQLe955g@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Precedence: bulk

On Wed, Oct 10, 2018 at 10:14:23PM +0900, fn ln wrote:
> Hello.
> 
> I've found this on the docs:
> https://www.postgresql.org/docs/devel/static/plpgsql-control-structures.html#
> PLPGSQL-STATEMENTS-RETURNING-PROCEDURE
> > If a RETURN statement is desired to exit the code early, then NULL must be
> returned.
> 
> But isn't actual syntax just RETURN without an expression?

I think you might be right:

	CREATE OR REPLACE PROCEDURE triple()
	LANGUAGE plpgsql
	AS $$
	BEGIN
	        RETURN NULL;
	END;
	$$;
	ERROR:  RETURN cannot have a parameter in a procedure
-->	LINE 5:         RETURN NULL;
	                       ^

	CREATE OR REPLACE PROCEDURE triple()
	LANGUAGE plpgsql
	AS $$
	BEGIN
	        RETURN;
	END;
	$$;

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +