Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1aMcdD-0000xM-LT for pgsql-docs@arkaria.postgresql.org; Fri, 22 Jan 2016 14:24:07 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1aMcdD-0004Vj-4u for pgsql-docs@arkaria.postgresql.org; Fri, 22 Jan 2016 14:24:07 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1aMccq-000470-Tz for pgsql-docs@postgresql.org; Fri, 22 Jan 2016 14:23:45 +0000 Received: from mail-yk0-x236.google.com ([2607:f8b0:4002:c07::236]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1aMccn-00060F-63 for pgsql-docs@postgresql.org; Fri, 22 Jan 2016 14:23:44 +0000 Received: by mail-yk0-x236.google.com with SMTP id v14so87582281ykd.3 for ; Fri, 22 Jan 2016 06:23:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=ux5ZeShWk0uhVa7kKXo/0dUisjLyCAzFXTBoinaQfOE=; b=gIvxMbfi+1vF0Lvr5j4/iyvFfs72eBhvohHZ1d55FewpkuhPwXKJogdowDS3aWRQMk JqwisM2TnRmAKpbcRJ0Y5z82j4GCxeHAHr91UHw04VyYKipxrJ8zw15wRRu4D07KW8N/ DEt7Pq0zq6W2B8UEoWvJT1Tw7i2d/TcBUdQ0ixpuvJD8xIbBx1zP8xdGQjHOochOvxhY QwOqzMK2RkpmVc+fkB9SpZuHgMBEWJ813Hit43dWkQcHqgeyk1bhSdzOWGm34+p9kl0C w/NRstseL7/gAIkat+mYzDLkdCoUnBVSDo7mkssMCRpIfPvhY8BOHJKwJBkz2nryOjoR 2zvg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=ux5ZeShWk0uhVa7kKXo/0dUisjLyCAzFXTBoinaQfOE=; b=S6/oT9WX+NRK0YjRQMRTN8W5IyLk/sCO6DPrppMKXAsHny3GUJpgxr9BwAFjiaOgyY PYZWgUYPOuFPWw+IXGSMGVsTb4FTWtMB9hbJ/q+FW4jCAftTLL1BR1R6LM+DnWZSjb0x /xrOxJSP8M67Sffyt7Ij1ROIVpLLthngi9mGkuE3iJT1MBcXTngqRcUEFxKXIM6bIvih t48JLlPySxoq4jC8RFaqWOACzYrrnspebV+IVk76wPXlnGxKGWIM4rcQoOzlqVhsKXHM +anlRTVwnOCrK7q4nLi7XSB2IYTr0VPDn2wXMa/lbYqTwywPs6HFcITKx9I35fHzSDUl nJUg== X-Gm-Message-State: AG10YOTOgqIf7gnov2Je29dqSuF2sa1Y8m5u0nGF6h+f1GXgzVn0Vt4kArXPfEwLCt8uWHHjpULaDAxHxYzZyQ== X-Received: by 10.129.88.193 with SMTP id m184mr1590249ywb.332.1453472618403; Fri, 22 Jan 2016 06:23:38 -0800 (PST) MIME-Version: 1.0 From: Johannes Choo Date: Fri, 22 Jan 2016 14:23:29 +0000 Message-ID: Subject: s/user/role/ in section 5.6 of v9.5.0 and 9.6devel of docs. To: pgsql-docs@postgresql.org Content-Type: multipart/alternative; boundary=001a11492cea1c5c940529ecf75c X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --001a11492cea1c5c940529ecf75c Content-Type: text/plain; charset=UTF-8 Hi, I think section 5.6 of v9.5.0 and 9.6devel can benefit from changing some occurrences of the word 'user' to 'role. Specifically, in "For example, if joe is an existing user" and "The special "user" name PUBLIC can be used to grant a privilege to every user on the system.", it is ambiguous whether "user" refers to any role, or a role with a LOGIN privilege, especially when you consider that CREATE USER is shorthand creating a role with LOGIN privileges. Bests, Johannes Choo --001a11492cea1c5c940529ecf75c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,

I think section 5.6 of v9.5.0 and 9= .6devel can benefit from changing some occurrences of the word 'user= 9; to 'role. Specifically, in

"For example, if=C2=A0joe=C2=A0is an existing user"

and

"The special=C2=A0"user"=C2=A0name=C2=A0PUBLIC=C2=A0can be used to grant a privilege to every user on the= system.",

it is ambiguous whether "user" = refers to any role, or a role with a LOGIN privilege, especially when you c= onsider that CREATE USER is shorthand creating a role with LOGIN privileges= .

Bests,
Joha= nnes Choo
--001a11492cea1c5c940529ecf75c--