Horton

Re: BUG #15555: Syntax errors when using the COMMENT command in plpgsql and a "comment" variable

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, feikesteenbergen@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Date: 2019-01-04T14:09:48Z
Lists: pgsql-bugs 
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.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Support plpgsql variable names that conflict with unreserved SQL keywords.

  2. De-reserve most statement-introducing keywords in plpgsql.