Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1arTWa-0008Nw-0H for pgsql-docs@arkaria.postgresql.org; Sat, 16 Apr 2016 16:56:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1arTWZ-0007FY-J5 for pgsql-docs@arkaria.postgresql.org; Sat, 16 Apr 2016 16:56:47 +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_2) (envelope-from ) id 1arTWX-0007AR-OF for pgsql-docs@postgresql.org; Sat, 16 Apr 2016 16:56:46 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1arTWU-0000Gl-BD for pgsql-docs@postgresql.org; Sat, 16 Apr 2016 16:56:45 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 689BA218C4 for ; Sat, 16 Apr 2016 12:56:40 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 16 Apr 2016 12:56:40 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=eisentraut.org; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=zNdhRlnA8BchRh0O8KGfaHZtRPM=; b=APmXit fCvxQm/hczvZNgF8DUQxLE01lBM9k6JFRoR4X6npj6Jsgz9YyZ5wPsu6topwQbz6 sQ+teJXeA2EfGAFfv38sYW3W8UxIJIZk3VkHtAFOi30nHRs2OaA/aRIMpQJozpNv YPbUwyHIoE6C5Qv2aAoQeEk4gzO+qhqVo1/ls= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=zNdhRlnA8BchRh0 O8KGfaHZtRPM=; b=eZ7VLGvmoEZfA6p2x2EERllSfR0pUH44zEJRcXjl4hR0FIN foxoSAdYTrCaIqlpTObkp88EwxcyaBjrf9zz0A/3OMYjaHcgOfU6LwNMqCkuYn+A l/X0HieFBPPA40KCuUHLFki1jS5lcHVl4rLeO4qXSF6vk+PCh4FBCqQdcLx8= X-Sasl-enc: 6nH/CkM/AwXNFnqvlBaBAcoBTMsiWeJ/PcBTvnVWpvcb 1460825800 Received: from vanquo.pezone.net (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 22E8EC00012; Sat, 16 Apr 2016 12:56:40 -0400 (EDT) Subject: Re: s/user/role/ in section 5.6 of v9.5.0 and 9.6devel of docs. To: Johannes Choo , pgsql-docs@postgresql.org References: From: Peter Eisentraut Message-ID: <57126EC7.5010301@eisentraut.org> Date: Sat, 16 Apr 2016 12:56:39 -0400 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Icedove/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit 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 On 01/22/2016 09:23 AM, Johannes Choo wrote: > 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.", Done. These were the only two cases that were inconsistent, I think. -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs