Re: why semicolon after begin is not allowed in postgresql? - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: why semicolon after begin is not allowed in postgresql?
Date
Msg-id 1385414742.86872.YahooMailNeo@web162905.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: why semicolon after begin is not allowed in postgresql?  (AK <alkuzo@gmail.com>)
List pgsql-hackers
AK <alkuzo@gmail.com> wrote:

> I do see your logic now, but this thing is a common mistake - it
> means that this seems counter-intuitive to some people. What
> would happen if we applied Occam's razor and just removed this
> rule?
>
> All existing code would continue to work as is, and we would have
> one less rule to memorize. That would make PostgreSql a slightly
> better product,
>
> right?

Possibly; but what happens if we want to use plpgsql syntax for
stored procedures which allow the BEGIN command some day?  We would
have lost the ability to distinguish that command from the start of
a compound statement.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Errors on missing pg_subtrans/ files with 9.3
Next
From: Heikki Linnakangas
Date:
Subject: Re: ToDo: fast update of arrays with fixed length fields for PL/pgSQL