Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE
Date
Msg-id CAFcNs+prwNO+p+PO8kMFEuBSSAVRU4WXqg5r8zQDpgEfwjXs4Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE  (Fabrízio de Royes Mello <fabriziomello@gmail.com>)
List pgsql-hackers
Tree view


On Fri, Jan 27, 2017 at 8:53 PM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
>
> On 1/26/17 1:20 PM, Fabrízio de Royes Mello wrote:
> > Ok, but doing in that way the syntax would be:
> >
> > COMMENT ON DATABASE CURRENT_DATABASE IS 'comment';
>
> Yes, that's right.  We also have ALTER USER CURRENT_USER already.
>

Ok, but if we make CURRENT_DATABASE reserved wouldn't it lead us to a conflict with current_database() function?

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog: http://fabriziomello.github.io
>> Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
>> Github: http://github.com/fabriziomello

pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)
Next
From: Fabrízio de Royes Mello
Date:
Subject: Re: [HACKERS] Add support to COMMENT ON CURRENT DATABASE