Support to COMMENT ON DATABASE CURRENT_DATABASE

From: Jing Wang <jingwangian(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Support to COMMENT ON DATABASE CURRENT_DATABASE
Date: 2017-06-05 01:09:03
Message-ID: CAF3+xM+xSswcWQZMP1cjj12gPz8DXHcM9_fT1y-0fVzxi9pmOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

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

Can't find the previous link in my email history list so create a new topic
here.

By using the patch the CURRENT_DATABASE as a keyword can be used in the
following SQL commands:

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

[1] https://www.postgresql.org/message-id/20150317171836.GC10492@momjian.us
[2]
https://www.postgresql.org/message-id/flat/CAB7nPqSTXUWAx-C5Pgw%2Bdu5jxu4QZ%3DaxQq165McmyT3UggWmuQ%40mail(dot)gmail(dot)com#CAB7nPqSTXUWAx-C5Pgw+du5jxu4QZ=axQq165McmyT3UggWmuQ(at)mail(dot)gmail(dot)com

--
Regards,
Jing Wang
Fujitsu Australia

Attachment Content-Type Size
comment_on_current_database_v2.patch text/x-patch 27.9 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-06-05 01:27:54 Re: Re: BUG #14680: startup process on standby encounter a deadlock of TwoPhaseStateLock when redo 2PC xlog
Previous Message Mark Kirkwood 2017-06-05 01:08:12 Re: logical replication - still unstable after all these months