| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add support to COMMENT ON CURRENT DATABASE |
| Date: | 2017-01-09 20:15:53 |
| Message-ID: | a97c6033-27e9-ab2e-4acf-8a671af98a6c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/9/17 2:52 PM, Alvaro Herrera wrote:
> CURRENT_USER is a standards-mandated keyword, but CURRENT_DATABASE is
> not. The closest thing SQL has is CURRENT_CATALOG, which is the string
> that identifies the "current default catalog". This would lead us to
> COMMENT ON DATABASE CURRENT_CATALOG
>
> Do we want that spelling? It looks ugly to me.
Hence my suggestion earlier to make CURRENT_DATABASE reserved.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-01-09 20:25:36 | Re: ICU integration |
| Previous Message | Peter Eisentraut | 2017-01-09 20:14:23 | Re: Add support to COMMENT ON CURRENT DATABASE |