On Sun, Jan 29, 2017 at 3:33 AM, Fabrízio de Royes Mello <fabriziome...@gmail.com> wrote: > On Sat, Jan 28, 2017 at 4:26 PM, Fabrízio de Royes Mello > <fabriziome...@gmail.com> wrote: >> On Fri, Jan 27, 2017 at 8:53 PM, Peter Eisentraut >> <peter.eisentr...@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?
Patch marked as returned with feedback as no new version has been provided for the last 2 weeks and a half. Please feel free to update if that's not adapted. The patch was waiting on author's input for some time by the way.. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
