Re: semicolon not required on END statement - Mailing list pgsql-bugs

From Tom Lane
Subject Re: semicolon not required on END statement
Date
Msg-id 4645.1096602412@sss.pgh.pa.us
Whole thread Raw
In response to Re: semicolon not required on END statement  (Neil Conway <neilc@samurai.com>)
Responses Re: semicolon not required on END statement
List pgsql-bugs
Neil Conway <neilc@samurai.com> writes:
> On Fri, 2004-10-01 at 01:11, Hussein Patni wrote:
>> I noticed in plpgsql that a semi colon is not always requiredafter
>> the END statement.

> Yeah, I've noticed this as well (although it doesn't appear to be
> documented). Would we gain anything by enforcing this restriction? IMHO
> not a lot...

We specifically do not require a semicolon at the very end of the
function definition.  My recollection is that the plpgsql grammar did
originally enforce that, and we relaxed it because it confused people.
You have to admit that
    ... END;';
is a bit odd-looking.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: PLPGSQL and FOUND stange behaviour after EXECUTE
Next
From: Neil Conway
Date:
Subject: Re: semicolon not required on END statement