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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: feikesteenbergen(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15555: Syntax errors when using the COMMENT command in plpgsql and a "comment" variable
Date: 2019-01-04 17:18:24
Message-ID: 7799.1546622304@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-01-04 18:04:41 Re: SELECT do not return all rows depending on selected columns
Previous Message Hugh Ranalli 2019-01-04 16:29:42 Re: BUG #15548: Unaccent does not remove combining diacritical characters