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+xMK2xt_CF6vTDcwN=icDcTZ2YJpc8PBPGJCP+688-bDFTA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Surafel Temesgen <surafel3000@gmail.com>)
Responses Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Jing Wang <jingwangian@gmail.com>)
List pgsql-hackers
Hi Surafel,

>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.

Thanks your review and suggestion. I will add them.


Regards,
Jing Wang
Fujitsu Australia

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256
Next
From: vinayak
Date:
Subject: Re: [HACKERS] ECPG: WHENEVER statement with DO CONTINUE action