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 1n7KcR-0006ZI-4M for pgsql-docs@arkaria.postgresql.org; Tue, 11 Jan 2022 17:07:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n7KcQ-0003D1-0u for pgsql-docs@arkaria.postgresql.org; Tue, 11 Jan 2022 17:07:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n7KcP-0003Cr-L9 for pgsql-docs@lists.postgresql.org; Tue, 11 Jan 2022 17:07:33 +0000 Received: from mail-ed1-x52f.google.com ([2a00:1450:4864:20::52f]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n7KcM-0000cM-T2 for pgsql-docs@lists.postgresql.org; Tue, 11 Jan 2022 17:07:32 +0000 Received: by mail-ed1-x52f.google.com with SMTP id c71so58337549edf.6 for ; Tue, 11 Jan 2022 09:07:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=8EWt0BJXpi4eM9O5iQOV0OADQtWcOt64q54P8YqglYA=; b=KHHrsNKOz2d9NmGzyrBFi2esDVMA7TeFYm+AzKGpGf1dkq6QO8umXGNZydKwIKz7QT K9NobHNcHUDgog5dE8PDaZtC9vyRImGMVdycZnALIOiKjSkZLkUhDVIU5+0neY40ZWJn JJ/EdQd/1SyWh/lKwftJgy+ID3O8+UMKXiy5CEzx5yw2nap1ulxD8WE9BYzyUZfXIAxJ ExlNtvwlL8GSfdRnuEBflYjWx8zEsGTGFAMWHJRezoP5t6XtuJnS/RVTDA1o2bKz3nxO HUWLm/EHBNYCZ/FLRWvE1O8t7FhUY9ErZSMuOurmgoj+iz2MBVshhVe32tU1wB4KseF4 fwlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=8EWt0BJXpi4eM9O5iQOV0OADQtWcOt64q54P8YqglYA=; b=GNz6poVM5PBeuqsVT2nPtkLKV8S7LDK1RF/eUD5kZPlLbiU3Iix5lgI/VcnMWj2DmP 4r018splosszGVh8UCsFi5dJnE22QR8ous1WraOzu4HVjRhP+swazAySNWVBwx+YvF5T c+EDjUoMkQZBK9u2u1LAmWtub7Qu4725ttzJkPf3cCsbUMyxS7L9GQTCGWCZNTrj9f7A BlxjVjHlHv6pSx411oD/njqKIu/MXTHHaQ8qiYEnDdbFRNGxQkJF8mycwHz1B841Jr2w PmKgSb9810wjqUlIpxxzERvC0TlIbtzXitSVpXss6Pjk+6IcAIsiaeQ6/KaZPJsZA4uz yZYQ== X-Gm-Message-State: AOAM5320+yHfWs8qn9zL/9bvihqu6XurGLauIonygm/+GvYXH8BWFuHx L2RW/jt4oVY/paB8kCyMu/CzKvvyC+q7FQ== X-Google-Smtp-Source: ABdhPJz3OyWXtTQUkEyEsypvVvzSqRtKlrRMb1srLo0j5NhLKGcqnsUd8Axeb0z9bjcLI2Sy+qPZpg== X-Received: by 2002:aa7:df18:: with SMTP id c24mr5187995edy.164.1641920849065; Tue, 11 Jan 2022 09:07:29 -0800 (PST) Received: from localhost.localdomain (mobiledyn-62-240-134-64.mrsn.at. [62.240.134.64]) by smtp.gmail.com with ESMTPSA id dd5sm3806843ejc.99.2022.01.11.09.07.27 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Jan 2022 09:07:28 -0800 (PST) Message-ID: Subject: Re: Question about role attributes docs From: Laurenz Albe To: Shinya Kato , pgsql-docs@lists.postgresql.org Date: Tue, 11 Jan 2022 18:07:25 +0100 In-Reply-To: <1ecdb1ff78e9b03dfce37e85eaca725a@oss.nttdata.com> References: <1ecdb1ff78e9b03dfce37e85eaca725a@oss.nttdata.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2022-01-11 at 16:40 +0900, Shinya Kato wrote: > I have a question about the documentation on ROLE. > > According to [1], INHERIT and BYPASSRLS can be specified when executing > the CREATE ROLE command. However, there is no such description in Role > Attributes in [2]. Are these concepts different from Role Attributes? Or > are they just not documented? If they need to be documented, I'll create > a patch. > > [1] https://www.postgresql.org/docs/devel/sql-createrole.html > [2] https://www.postgresql.org/docs/devel/role-attributes.html I think that is indeed an omission, and adding documentation would be a good idea. On the other hand, a lot of that information is more or less a duplicate of the CREATE ROLE documentation. I wonder if the latter page could be removed altogether. Yours, Laurenz Albe