Re: Support to COMMENT ON DATABASE CURRENT_DATABASE

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Jing Wang <jingwangian(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support to COMMENT ON DATABASE CURRENT_DATABASE
Date: 2017-06-05 01:30:13
Message-ID: CAB7nPqSJKD=xuL5T8L-V-hHE21Xp7SWe=LM02yMRVfuMnCn4oQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 5, 2017 at 10:09 AM, Jing Wang <jingwangian(at)gmail(dot)com> wrote:
> By using the patch the CURRENT_DATABASE as a keyword can be used in the
> following SQL commands:
>
> 1. COMMENT ON DATABASE CURRENT_DATABASE is ...
> 2. ALTER DATABASE CURRENT_DATABASE OWNER to ...
> 3. ALTER DATABASE CURRENT_DATABASE SET parameter ...
> 4. ALTER DATABASE CURRENT_DATABASE RESET parameter ...
> 5. SELECT CURRENT_DATABASE

You should add that to the next commit fest:
https://commitfest.postgresql.org/14/
Note that it may take a couple of months until you get some review, as
the focus now is to stabilize Postgres 10.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-06-05 01:31:12 Re: logical replication and PANIC during shutdown checkpoint in publisher
Previous Message Andres Freund 2017-06-05 01:29:31 Re: logical replication and PANIC during shutdown checkpoint in publisher