From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
cc: feikesteenbergen@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15555: Syntax errors when using the COMMENT command in
 plpgsql and a "comment" variable
In-reply-to: <52614d45-ca8d-5682-d532-8d1f2f2dbd9c@2ndquadrant.com>
References: <15555-149bbd70ddc7b4b6@postgresql.org>
 <31368.1545078376@sss.pgh.pa.us> <32114.1545079626@sss.pgh.pa.us>
 <23647.1545084358@sss.pgh.pa.us>
 <52614d45-ca8d-5682-d532-8d1f2f2dbd9c@2ndquadrant.com>
Comments: In-reply-to Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
	message dated "Fri, 04 Jan 2019 15:09:48 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7798.1546622304.1@sss.pgh.pa.us>
Date: Fri, 04 Jan 2019 12:18:24 -0500
Message-ID: <7799.1546622304@sss.pgh.pa.us>
Precedence: bulk

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