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 1nIF7O-0000Bg-VP for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Feb 2022 19:28:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nIF7N-0002td-TQ for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Feb 2022 19:28:37 +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 1nIF7N-0002tT-Kj for pgsql-hackers@lists.postgresql.org; Thu, 10 Feb 2022 19:28:37 +0000 Received: from mail-pj1-x1031.google.com ([2607:f8b0:4864:20::1031]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nIF7L-0006fh-2C for pgsql-hackers@postgresql.org; Thu, 10 Feb 2022 19:28:37 +0000 Received: by mail-pj1-x1031.google.com with SMTP id r64-20020a17090a43c600b001b8854e682eso6619592pjg.0 for ; Thu, 10 Feb 2022 11:28:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=+KFzrtiMAvpMZbWDO+X/M2P04WAuMBvfYVh8fqyAP+U=; b=TCuGCmnY6ORUfGZjNhItWK9gDXkkXOmDTlfBsoLsSzPMdpxwP6tbiZIHGKOuC5+Q1g seNNFk4UF6SdMVRMo9tVhBO+PGoPw6/ojFX+Sn86k5SWA7yiKU9qll8ACd3wdmuI83sp VyYagkNwPsmUZMV8MWV/XtWxxBA1t+nOVSOeo3I/4/Y72hFLV7pmDFecd3ZbBnNrxxLf uBOs7gR2+mWlEmaKer7/zLoiLNO+KWkgX699gXdr7qXkImDi2F6IRm1VZbIhaKoQPdMW cI9agA191BscXvxmyzBgqkcgncI9O3WXTjRbeYEFnYYDc6z39R5lwtFJzu3M2+cLby5p HEzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=+KFzrtiMAvpMZbWDO+X/M2P04WAuMBvfYVh8fqyAP+U=; b=ddmug7uqdw98+5UoU05XFfb2ljJujSycQa8bn6Kh1BHoDysw0tGUh9ntJ3msdJKstw xYgJXxtIMWzMqDRRYrZfkoPMDckNryCY3BHgS87IqcJS+4urU/Bot/ILLBLz5p3RxMAX 7C9QDFnYbmfTbMtrOR/d9Iqb9DPDOraz2VoY4jP5JC6mf8EmQXD2yJB9M2p1e32RLk5R a40UQ7vCBEpNSCjcVDyH8XiXgrDPOCWJHqChyBQEKz97mROCTTPGNA49EWhLPg0xUU0Z aYeQeO/7EigYAVNK+CW58UGlGRkv9WMEP4EpEjt93ycG3wGgSI6zSOnFYvSpF01trd7g awcQ== X-Gm-Message-State: AOAM533ZsQVFl999LsslWT2STpmwQmEa1diVyR9XqMHmyWbEnD3huwOO xW3BBx5aIXxDqA2QfApYNcI= X-Google-Smtp-Source: ABdhPJwFKuA7O0H2hlh20/QC61zAhNYNtaQsmeIU7KrqBJ5wEMppfdUW4qLSN6rCXLTINkm6nigUKA== X-Received: by 2002:a17:902:d64a:: with SMTP id y10mr8777982plh.66.1644521312703; Thu, 10 Feb 2022 11:28:32 -0800 (PST) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id n37sm8043782pgl.48.2022.02.10.11.28.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 10 Feb 2022 11:28:32 -0800 (PST) Date: Thu, 10 Feb 2022 11:28:29 -0800 From: Nathan Bossart To: Joe Conway Cc: Robert Haas , Joshua Brindle , Tom Lane , "Bossart, Nathan" , Stephen Frost , PostgreSQL-development Subject: Re: [PATCH v2] use has_privs_for_role for predefined roles Message-ID: <20220210192829.GB1684442@nathanxps13> References: <80af9ba7-ec24-9134-8fd9-00bf13f5c494@joeconway.com> <18eab9b6-1f77-72b2-83d3-1856c17f3fcb@joeconway.com> <0b1b6cfb-d752-28f6-7ccb-993998be0189@joeconway.com> <20220209181333.GD1627503@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Feb 09, 2022 at 04:39:11PM -0500, Joe Conway wrote: > On 2/9/22 13:13, Nathan Bossart wrote: >> I do wonder if users find the differences between predefined roles and role >> attributes confusing. INHERIT doesn't govern role attributes, but it will >> govern predefined roles when this patch is applied. Maybe the role >> attribute system should eventually be deprecated in favor of using >> predefined roles for everything. Or perhaps the predefined roles should be >> converted to role attributes. > > Yep, I was suggesting that the latter would have been preferable to me while > Robert seemed to prefer the former. Honestly I could be happy with either of > those solutions, but as I alluded to that is probably a discussion for the > next development cycle since I don't see us doing that big a change in this > one. I agree. I still think Joshua's proposed patch is a worthwhile improvement for v15. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com