Re: BUG #13708: strange behaviour instead of syntax error

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.