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

From Robert Haas
Subject Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE
Date
Msg-id CA+TgmoZJ3Oo0Lk7-jNKEVPK9HQm5oCRQKe5F1OHwceeMtSBHhw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Support to COMMENT ON DATABASE CURRENT_DATABASE  (Jing Wang <jingwangian@gmail.com>)
List pgsql-hackers
On Wed, Nov 29, 2017 at 11:35 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Mon, Nov 27, 2017 at 11:41 AM, Jing Wang <jingwangian@gmail.com> wrote:
>> This is a patch for current_database working on ALTER ROLE/GRANT/REVOKE
>> statements which should be applied after the previous patch
>> "comment_on_current_database_no_pgdump_v4.4.patch".
>>
>> By using the patch the CURRENT_DATABASE can working in the following SQL
>> statements:
>>
>> ALTER ROLE ... IN DATABASE CURRENT_DATABASE SET/RESET
>> configuration_parameter
>> GRANT ... ON DATABASE CURRENT_DATABASE TO role_specification ...
>> REVOKE ... ON DATABASE CURRENT_DATABASE FROM ...
>
> Moved to next CF with same status, "needs review".

Patch no longer applies.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pl/perl extension fails on Windows
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager