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 1oiJFe-0001Nk-7b for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Oct 2022 17:41:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oiJFc-0008W4-4s for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Oct 2022 17:41:08 +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 1oiJFb-0008Vv-QC for pgsql-hackers@lists.postgresql.org; Tue, 11 Oct 2022 17:41:07 +0000 Received: from mail-pf1-x42e.google.com ([2607:f8b0:4864:20::42e]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oiJFX-0003tr-VF for pgsql-hackers@postgresql.org; Tue, 11 Oct 2022 17:41:07 +0000 Received: by mail-pf1-x42e.google.com with SMTP id 67so14152512pfz.12 for ; Tue, 11 Oct 2022 10:41:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=d/UOwRPk5lvYg8Sm2WdcEcyAL/VJlSr9G48amD3of8I=; b=KlLGeI/R8WJnzSoEvd1RAQdOWfiV1NXq0tgUTfGhqYd5UpUKVOsC7ZMm47QyTVlECo 5ZU4j1DSU6A2DSnO2jMixMec1BZiV/1JnTY5ignLSTOv+eDYr8IJ63J0WZSBlbe5VYn3 5Ypo2qfnIb4/4g8/i/g3xvODkwjiE20VffwH3gNRxf1/6X22aZvUonAHmDVEK+2kSpM0 Rk0eP8YCJf/04t2DEByu+3sntyXhRYj853dCruKwyk34Q/SIDh2EAo/Dilf3BE1cDlMk zkfaML1k5zzqs4pD3+exD49kd5Xe3p0xNOjTo17Fw0MyF607RYot4Y5W+O05f6Y7ASMN ISHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=d/UOwRPk5lvYg8Sm2WdcEcyAL/VJlSr9G48amD3of8I=; b=GddiKZTeSnRpf9LbU09mKbAd040f9U3XBgkuUbZANoqsD3XtTEZYHHf+DuRCwGp0FO BVatFDHbKXOKD3w/z+jsqcc3m+K8U8bc5xYoOM2KRLeExpuJJLgDtQHpWYoZRIPbXAkw sZ6CuD7wKkZ2hekdxzvvbEWtfs5CvyR6wquSfs8rRaxBzgcls735KHF72mCVUVRIgCkY rWVh+c1mdIIQrQLc1YB+u4uScxdw5suQ6U/DdOrKjY7zeCXowfLWYAVPXOqUs1Bpb4Tn HP3vhw4GrweNqqlY0YPdXzAMqx2FZtqN90RcAImwt4lG+Bv2UKW2jw1P7SiKT88h7j6D +1Vw== X-Gm-Message-State: ACrzQf2i8CefOYKQSy0u++YeKuHODFCt3XvXK0fcTqUv1h6xVoZTYWEz hwN/I4+ESlOvNwy5V6SCk/g= X-Google-Smtp-Source: AMsMyM4lKvW7WrIDGh1WujTClkAXG1XMq7yOVNdXJkETk+AGXabCKlOki842IKHXV0/V5wJa8SWpJw== X-Received: by 2002:a65:62c7:0:b0:463:9c67:5fe2 with SMTP id m7-20020a6562c7000000b004639c675fe2mr6516655pgv.443.1665510062202; Tue, 11 Oct 2022 10:41:02 -0700 (PDT) Received: from nathanxps13 ([50.47.162.83]) by smtp.gmail.com with ESMTPSA id g5-20020aa796a5000000b00561d79f1064sm9293326pfk.57.2022.10.11.10.41.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Oct 2022 10:41:01 -0700 (PDT) Date: Tue, 11 Oct 2022 10:40:59 -0700 From: Nathan Bossart To: Michael Paquier Cc: "David G. Johnston" , Robert Haas , Tom Lane , Joe Conway , Joshua Brindle , PostgreSQL-development Subject: Re: use has_privs_of_role() for pg_hba.conf Message-ID: <20221011174059.GA1326442@nathanxps13> References: <3347532.1665173939@sss.pgh.pa.us> <20221007215836.GB814385@nathanxps13> <87994809-5b2c-08f0-0ab3-3c76c49afada@joeconway.com> <3574712.1665242046@sss.pgh.pa.us> <20221008171222.GB825354@nathanxps13> <20221009211348.GB900071@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 Tue, Oct 11, 2022 at 02:01:07PM +0900, Michael Paquier wrote: > Thanks, applied. It took me a few minutes to note that > regress_regression_* is required in the object names because we need > to use the same name for the parent role and the database, with > "regress_" being required for the role and "regression" being required > for the database. I have added an extra section where pg_hba.conf is > set to match only the parent role, while on it. perltidy has reshaped > things in an interesting way, because the generated log_[un]like is > long, it seems. Thanks! -- Nathan Bossart Amazon Web Services: https://aws.amazon.com