| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, yozh(dot)ne(at)gmail(dot)com |
| Subject: | Re: BUG #13708: strange behaviour instead of syntax error |
| Date: | 2015-10-24 12:04:53 |
| Message-ID: | CAM-w4HOtgpKttkptZu0D5Uv5d1yiqiWn9m1Hhv5Hqy=LGsKvGA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 24 Oct 2015 00:03, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2015-10-24 17:28:17 | Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica. |
| Previous Message | Michael Paquier | 2015-10-24 11:08:28 | Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica. |