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

From Jing Wang
Subject [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
Date
Msg-id CAF3+xM+xSswcWQZMP1cjj12gPz8DXHcM9_fT1y-0fVzxi9pmOw@mail.gmail.com
Whole thread Raw
Responses Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
List 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.gmail.com#CAB7nPqSTXUWAx-C5Pgw+du5jxu4QZ=axQq165McmyT3UggWmuQ@mail.gmail.com

--
Regards,
Jing Wang
Fujitsu Australia

Attachment

pgsql-hackers by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: [HACKERS] logical replication - still unstable after all thesemonths
Next
From: Michael Paquier
Date:
Subject: [HACKERS] Re: BUG #14680: startup process on standby encounter a deadlock ofTwoPhaseStateLock when redo 2PC xlog