Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ljmSi-0000GQ-Jr for pgsql-docs@arkaria.postgresql.org; Thu, 20 May 2021 17:27:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ljmSg-0006Ox-Eu for pgsql-docs@arkaria.postgresql.org; Thu, 20 May 2021 17:27:54 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ljmSg-0006Op-6o for pgsql-docs@lists.postgresql.org; Thu, 20 May 2021 17:27:54 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ljmSd-0008UJ-GU for pgsql-docs@lists.postgresql.org; Thu, 20 May 2021 17:27:53 +0000 Received: from [10.0.1.8] (unknown [188.123.231.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id D2F5521C618E for ; Thu, 20 May 2021 20:27:49 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1621531669; bh=hsjgwzT/Su13SgRG6U7cAXSTBi9gH5ByEhFxOt9OopM=; h=Subject:To:References:From:Date:In-Reply-To; b=IvI6u1KP50eaibA6BPCSSbhZXD1IhKT4UvOwzwBJpeeUwWuzZ8lhHhtMTiXIYqs+I qkGKyiAhUysfSnQaNBA1j+TpOzTV1nroHMu3BnzqOmWKAHjABfh9JeZkFdbZ1tFz6G SaXscoY9twVWJxRkRL+HHRiDm4PtGIP7yPwMJ8gU= Subject: Re: pg_monitor role description To: pgsql-docs@lists.postgresql.org References: <162149110071.26171.15811576640435665698@wrigleys.postgresql.org> <7018bb3a-26f1-a9be-1659-3bdafd122669@postgrespro.ru> <3690478.1621526623@sss.pgh.pa.us> From: Pavel Luzanov Message-ID: <5692728c-f0f3-c888-e5e9-19efd4051198@postgrespro.ru> Date: Thu, 20 May 2021 20:27:48 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <3690478.1621526623@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------A008498F8B15DE4016CF94F2" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------A008498F8B15DE4016CF94F2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello, On 20.05.2021 19:03, Tom Lane wrote: > Pavel Luzanov writes: >> Let me try one more time. >> What is correct from the English language point of view: >> 1. Julien Rouhaud is a member of PostgreSQL Community. >> or >> 2. PostgreSQL Community is a member of Julien Rouhaud, Michael Paquier. >> Or both forms are correct? >> I think that 1 is correct. > You're right about that ... So, is it correct to change description of pg_monitor role from: "Read/execute various monitoring views and functions. This role is a member of|pg_read_all_settings|,|pg_read_all_stats| and|pg_stat_scan_tables|." to "Read/execute various monitoring views and functions. The roles pg_read_all_settings, pg_read_all_stats and pg_stat_scan_tables are members of this role." I can prepare a simple patch. >> And column header in a \du output must be something like 'members' instead of 'member of'. > ... but this does not follow, because it's a poor analogy. "Member of" > means "these role(s) have been GRANT'ed to pg_monitor". Yes, I understood this point and agree. -- Pavel Luzanov Postgres Professional: https://postgrespro.com The Russian Postgres Company --------------A008498F8B15DE4016CF94F2 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
Hello,
On 20.05.2021 19:03, Tom Lane wrote:
Pavel Luzanov <p.luzanov@postgrespro.ru> writes:
Let me try one more time.
What is correct from the English language point of view:
1. Julien Rouhaud is a member of PostgreSQL Community.
or
2. PostgreSQL Community is a member of Julien Rouhaud, Michael Paquier.
Or both forms are correct?
I think that 1 is correct.
You're right about that ...

    
So, is it correct to change description of pg_monitor role from:
"Read/execute various monitoring views and functions. This role is a member of pg_read_all_settings, pg_read_all_stats and pg_stat_scan_tables."
to
"Read/execute various monitoring views and functions. The roles pg_read_all_settings, pg_read_all_stats and pg_stat_scan_tables are members of this role."

I can prepare a simple patch.

    
And column header in a \du output must be something like 'members' instead of 'member of'.
... but this does not follow, because it's a poor analogy.  "Member of"
means "these role(s) have been GRANT'ed to pg_monitor".
Yes, I understood this point and agree.

-- 
Pavel Luzanov
Postgres Professional: https://postgrespro.com
The Russian Postgres Company
--------------A008498F8B15DE4016CF94F2--