Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE

Поиск
Список
Период
Сортировка
От Surafel Temesgen
Тема Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
Дата
Msg-id CALAY4q83yJhmX_a0go_Tg=tB=B7wVC-wpL4HQbVPfBOTMraUiQ@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Jing Wang <jingwangian@gmail.com>)
Ответы Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Jing Wang <jingwangian@gmail.com>)
Список pgsql-hackers
Дерево обсуждения


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 по дате отправления:

Предыдущее
От: Tatsuo Ishii
Дата:
Сообщение: [HACKERS] Restrictions of logical replication
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: [HACKERS] logical replication: \dRp+ and "for all tables"