Re: BUG #15555: Syntax errors when using the COMMENT command in plpgsql and a "comment" variable
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: feikesteenbergen@gmail.com, pgsql-bugs@lists.postgresql.org
Date: 2019-01-04T17:18:24Z
Lists: pgsql-bugs
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > On 17/12/2018 23:05, Tom Lane wrote: >> [ pokes at that for a bit ] The logic here is a bit denser than >> one could wish, but here's a draft patch that seems to get the >> job done. It passes check-world, which isn't conclusive but >> at least suggests that this doesn't break anything. > This looks good to me. I can't think of any other syntax scenarios that > it needs to address. Pushed, thanks for checking! regards, tom lane
Commits
-
Support plpgsql variable names that conflict with unreserved SQL keywords.
- 4879a5172af0 12.0 landed
-
De-reserve most statement-introducing keywords in plpgsql.
- bb1b8f694ad2 9.5.0 cited