Postgres Pro
Downloads
Home   >   mailing lists

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

From Surafel Temesgen
Subject Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
Date
Msg-id CALAY4q83yJhmX_a0go_Tg=tB=B7wVC-wpL4HQbVPfBOTMraUiQ@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Jing Wang <jingwangian@gmail.com>)
Responses Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Jing Wang <jingwangian@gmail.com>)
List pgsql-hackers
Tree view


On Mon, Jun 5, 2017 at 4:09 AM, Jing Wang <jingwangian@gmail.com> wrote:
Hi all,

The attached patch is to support the feature "COMMENT ON DATABASE CURRENT_DATABASE". The solution is based on the previous discussion in [2] .

Your patch doesn't cover security labels on databases which have similar issue 
and consider dividing the patch into two one for adding CURRENT_DATABASE as a
database specifier and the other for adding database-level information to pg_dump output 
in a way that allows to load a dump into a differently named database

Regards,

Surafel 

pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: [HACKERS] Restrictions of logical replication
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] logical replication: \dRp+ and "for all tables"