From: | Jing Wang <jingwangian(at)gmail(dot)com> |
---|---|
To: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Support to COMMENT ON DATABASE CURRENT_DATABASE |
Date: | 2017-06-20 04:36:29 |
Message-ID: | CAF3+xMK2xt_CF6vTDcwN=icDcTZ2YJpc8PBPGJCP+688-bDFTA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | vinayak | 2017-06-20 04:51:25 | Re: ECPG: WHENEVER statement with DO CONTINUE action |
Previous Message | Michael Paquier | 2017-06-20 04:11:06 | Re: [HACKERS] Channel binding support for SCRAM-SHA-256 |