Quick Links

Re: why semicolon after begin is not allowed in postgresql?

From:	AK <alkuzo(at)gmail(dot)com>
To:	pgsql-hackers(at)postgresql(dot)org
Subject:	Re: why semicolon after begin is not allowed in postgresql?
Date:	2013-11-25 20:42:04
Message-ID:	1385412124750-5780216.post@n5.nabble.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Kevin,

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?

--
View this message in context: http://postgresql.1045698.n5.nabble.com/why-semicolon-after-begin-is-not-allowed-in-postgresql-tp5779905p5780216.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.

In response to

Re: why semicolon after begin is not allowed in postgresql? at 2013-11-22 22:43:06 from Kevin Grittner

Responses

Re: why semicolon after begin is not allowed in postgresql? at 2013-11-25 21:01:39 from Andrew Dunstan
Re: why semicolon after begin is not allowed in postgresql? at 2013-11-25 21:08:12 from David Johnston
Re: why semicolon after begin is not allowed in postgresql? at 2013-11-25 21:25:42 from Kevin Grittner
Re: why semicolon after begin is not allowed in postgresql? at 2013-11-25 21:36:44 from Mark Kirkwood

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Andres Freund	2013-11-25 20:52:25	Re: Errors on missing pg_subtrans/ files with 9.3
Previous Message	AK	2013-11-25 20:37:49	Re: Why is UPDATE with column-list syntax not implemented