Re: BUG #13708: strange behaviour instead of syntax error - Mailing list pgsql-bugs

From Greg Stark
Subject Re: BUG #13708: strange behaviour instead of syntax error
Date
Msg-id CAM-w4HOtgpKttkptZu0D5Uv5d1yiqiWn9m1Hhv5Hqy=LGsKvGA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #13708: strange behaviour instead of syntax error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #13708: strange behaviour instead of syntax error  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-bugs
On 24 Oct 2015 00:03, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
>
> Hmmm ... maybe just adding parens would do the trick.
>
> regression=# SELECT ('ERROR: No uncollected prize found!' RETURN);
> ERROR:  syntax error at or near "RETURN"
>
> That looks more promising ... though I'm not sure if there are
> any cases it would break.

That does seem like a good idea. There are plennty of keywords that can
follow a target list that would lead to strange behaviour, not the last of
which would be FROM... Adding parentheses should mean only a valid
expression should be accepted.

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.
Next
From: Jeff Janes
Date:
Subject: Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica.