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 1o76rf-00014V-DH for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Jul 2022 02:58:39 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o76re-0003II-AZ for pgsql-hackers@arkaria.postgresql.org; Fri, 01 Jul 2022 02:58:38 +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 1o76re-0003I9-0A for pgsql-hackers@lists.postgresql.org; Fri, 01 Jul 2022 02:58:38 +0000 Received: from mail-pj1-x1033.google.com ([2607:f8b0:4864:20::1033]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o76ra-0001MR-JG for pgsql-hackers@postgresql.org; Fri, 01 Jul 2022 02:58:37 +0000 Received: by mail-pj1-x1033.google.com with SMTP id dw10-20020a17090b094a00b001ed00a16eb4so1371517pjb.2 for ; Thu, 30 Jun 2022 19:58:34 -0700 (PDT) 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=9D1yLHnnEK3nrjd3cLDR73pAfBiu5AnyyFe8eqeV4tc=; b=onaAtHKG6EV/bCOR2GKihNZg4V3ThrJGDvKqLgFml12v/P2TVLySH+QadMOdXfW2qH LWYLPTUmxiKRoyS95FXKGjASiAcWYzEHSNsBGPIDkCArZqnFPN/jo0sl9VpGarFnYCFb Ov0r5ZwCrkDHTki0U/JKENzB5lYATeVehHa4yZmchY3IIxfTrlicIYNwfluUl0OcYZeQ GHnktXvhigqVmAGozZeDxpED3XA2KVbqn8OfcZA2UxEyyYVbAfhlfIRvPEhG/PKXoWdp DfW406uw6Zy6ZB2cKUowiH8DbTU/vKBgoQIURVuWxHb6oPm6bT9x0fKJ+kg/WDBy7YHO mMsA== 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=9D1yLHnnEK3nrjd3cLDR73pAfBiu5AnyyFe8eqeV4tc=; b=0TbhOesE0ucef/9joBblvo5ApXz1tCSMD0wRPVaJNtVFmYWv2zj5NZEsU7/ercseQU Ny802b+Dyo+ChJlPkQ+rrP//+PnHsKnAxWMSz16/aNEggLK9WDpQDt82UoGMLloxM9sG 3phmRbUbBENMqYLYYjcSBFLGkzfwy/fsvomMcQXv98F674bW/DZNXZyftVX1O3/mDYeg aINy/5awEyZhVCRDsBJjuNHionlGlf3S7NbS4zRCGSguzIOl0w/9zk58PaerkGkdGPRf O7H6uwKqX+sFXsh17mKV/9YHz8BVswt6YGfxc2SsCHbtuiKqqc2yBYM1MvOdxn9ivq0J 3Knw== X-Gm-Message-State: AJIora+21KXIcOPwrgKp2WxoJERp0Amoq5g24yMt+m9cp1cOtuX8UGcn lEdu9rqDCL15K3aveeRd3qs= X-Google-Smtp-Source: AGRyM1suXqFndnmBhkloSS/tqHcmOmy5PiwCtNootOpySBKHyG6kMwaEJtVaqKdFhLxUNCgesuy7og== X-Received: by 2002:a17:90b:3b4a:b0:1ed:38a0:d45f with SMTP id ot10-20020a17090b3b4a00b001ed38a0d45fmr15851419pjb.87.1656644312917; Thu, 30 Jun 2022 19:58:32 -0700 (PDT) Received: from nathanxps13 ([50.54.155.70]) by smtp.gmail.com with ESMTPSA id bc12-20020a170902930c00b0015e8d4eb1d5sm14217470plb.31.2022.06.30.19.58.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Jun 2022 19:58:32 -0700 (PDT) Date: Thu, 30 Jun 2022 19:58:30 -0700 From: Nathan Bossart To: Robert Haas Cc: Tom Lane , Joe Conway , "Bossart, Nathan" , Stephen Frost , PostgreSQL-development Subject: Re: replacing role-level NOINHERIT with a grant-level option Message-ID: <20220701025830.GA369935@nathanxps13> References: <730520.1644168290@sss.pgh.pa.us> <80af9ba7-ec24-9134-8fd9-00bf13f5c494@joeconway.com> <1066202.1654190251@sss.pgh.pa.us> <20220629231939.GA362451@nathanxps13> <20220630232931.GA367181@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 Thu, Jun 30, 2022 at 10:21:53PM -0400, Robert Haas wrote: > On Thu, Jun 30, 2022 at 7:29 PM Nathan Bossart wrote: >> IIUC you are suggesting that we'd leave rolinherit in pg_authid alone, but >> we'd add the ability to specify a grant-level option that would always take >> precedence. The default (WITH INHERIT DEFAULT) would cause things to work >> exactly as they do today (i.e., use rolinherit). Does this sound right? > > Yeah, that could be an alternative to the patch I proposed previously. > What do you (and others) think of that idea? I like it. If rolinherit is left in place, existing pg_dumpall scripts will continue to work, and folks can continue to use the role-level option exactly as they do today. However, we'd be adding the ability to use a grant-level option if desired, and it would be relatively easy to reason about (i.e., the grant-level option always takes precedence over the role-level option). Also, AFAICT this strategy still provides the full set of behavior that would be possible if only the grant-level option existed. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com