Re: plpgsql.print_strict_params - Mailing list pgsql-hackers

From Robert Haas
Subject Re: plpgsql.print_strict_params
Date
Msg-id CA+Tgmoa=7s4_+S8h7MfHMK6aHjFPdQW-BUQo0aHz6N04E=4BTA@mail.gmail.com
Whole thread Raw
In response to Re: plpgsql.print_strict_params  (Marko Tiikkaja <marko@joh.to>)
Responses Re: plpgsql.print_strict_params  (Marko Tiikkaja <marko@joh.to>)
List pgsql-hackers
On Sat, Sep 28, 2013 at 8:42 AM, Marko Tiikkaja <marko@joh.to> wrote:
> On 2013-09-28 12:31, Ian Lawrence Barwick wrote:
>> The patch looks good to me now; does the status need to be changed to
>> "Ready for Committer"?
>
> Yes.
>
> Thanks for reviewing!

This looks like a nice clean patch.  My only concern is that it makes
"on" and "off" unreserved plpgsql keywords.  It looks like that will
make them unusable as unquoted identifiers in a few contexts in which
they can now be used.  Has there been any discussion about whether
that's OK?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: logical changeset generation v6.2
Next
From: Steve Singer
Date:
Subject: Re: logical changeset generation v6.2