From: Tom Lane <tgl@sss.pgh.pa.us>
To: norbert.burza@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Wrong drop procedure example
In-reply-to: <156595338748.1297.13586621579809492028@wrigleys.postgresql.org>
References: <156595338748.1297.13586621579809492028@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Fri, 16 Aug 2019 11:03:07 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9204.1565962477.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 16 Aug 2019 09:34:37 -0400
Message-ID: <9205.1565962477@sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> I noticed that drop procedure with parenthesis doesn't work (procedure n=
ame
> not found), but without parenthesis it works. =

> Not OK: DROP PROCEDURE do_db_maintenance(); =

> OK: DROP PROCEDURE do_db_maintenance; =


Works for me:

regression=3D# create procedure do_db_maintenance() as 'begin end' languag=
e plpgsql;
CREATE PROCEDURE
regression=3D# DROP PROCEDURE do_db_maintenance(); =

DROP PROCEDURE

This depends, of course, on how you declared the procedure (with
or without any parameters).

If we wrote the example without parens, that would just move the
set of failure conditions around, so I'm unconvinced that it'd
be an improvement.

			regards, tom lane