Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE - Mailing list pgsql-hackers

From Jing Wang
Subject Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
Date
Msg-id CAF3+xMLTyf8OCbeNQw9TnfWxNriAzLy+jy0+LY5LNj4JmYwUOQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
Tree view
Hi Nathan,

Thanks for review comments.

Enclosed please find the patch which has been updated according to your suggestion.

The CURRENT_DATABASE can be used as following SQL statements and people can find information from sgml files:
    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. ALTER DATABASE CURRENT_DATABASE RESET ALL
    6. SELECT CURRENT_DATABASE
    7. SECURITY LABEL ON DATABASE CURRENT_DATABASE
    
As your mentioned the database_name are also present in the GRANT/REVOKE/ALTER ROLE, so a patch will be present later for supporting CURRENT_DATABASE on these SQL statements.

Regards,
Jing Wang
Fujitsu Australia
Attachment

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] Issues with logical replication
Next
From: Rushabh Lathia
Date:
Subject: With commit 4e5fe9ad19, range partition missing handling for the NULLpartition key