Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qQqii-001AgQ-Cb for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Aug 2023 14:51:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qQqig-007TUE-65 for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Aug 2023 14:51:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qQqif-007TU6-Sy for pgsql-hackers@lists.postgresql.org; Tue, 01 Aug 2023 14:51:31 +0000 Received: from mail-lf1-x12e.google.com ([2a00:1450:4864:20::12e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qQqia-000DOw-1J for pgsql-hackers@postgresql.org; Tue, 01 Aug 2023 14:51:30 +0000 Received: by mail-lf1-x12e.google.com with SMTP id 2adb3069b0e04-4fe28e4671dso4870964e87.0 for ; Tue, 01 Aug 2023 07:51:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690901482; x=1691506282; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=ly+Wjq6ZFAeOTCDmNUuvtvZWDoS+dpHfsLu+tmGRBtc=; b=ai2gEP26i4icRWTeGphbWrHAtQRDvDKhBKmigPAIY4xkghiaNYRWCahi4EfRO5PWSO Htd4OHGsjrcjJjLFmlaUUj/fQ+7UsPjaon9SpFNSWPSSqVtiBpavxN44RPbr3aSW8ZTx GBcHpWM/kkebktgZXAexws657vuxZZsr+6hm7oo9KYEXSpIhaaikF8aZ4Tw4JhYwDwyD RuqkCWlcWX7yh0db0ToUdcWrGDAbqOmeYEdaT2bXt9roTgxcEpkVuzK23tMoHPfrr3w1 HuR6FsEetCZqJGgUXGGCZFWN5PHYbNZbqNrsHx3xun4+VwbG+rMWxGx6t7ObouwyBN++ 9C2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690901482; x=1691506282; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=ly+Wjq6ZFAeOTCDmNUuvtvZWDoS+dpHfsLu+tmGRBtc=; b=UGJGABRKFOn66HyvjpHOMglPRiiIrSIimYh38d4bsYtvdrnVnYd1qx5feAoOn7TMC7 yIKaYUhrCLAkl24w1CWQpwc87PNbSplNNJM6IL5b0GvUQk/09Ksm1gm6qK2/xDHZnwoj atGF87qDV//g9jt/MZVU6BNu35eThgtDfEPsnm3OYOKPmXnPJJI0fLeu7nTNkarT1P7z JqnvLQsoEGc8BbGYySmf8E8++ecHsyYsgq9NVQOM9BEJ1ZvzawfqQ+DujKCzAZxyUce1 4GDwkgMEZeBySId/A1yjUF5nwDyE1MjRVJOpWszVlZJXNSaChjoMEpam+cSLw+oVi0Ia /DvA== X-Gm-Message-State: ABy/qLaOGh9czDrXvNtA0ofKlUALNXSc8sBBFrF6Ts/tQQN3jioUveOe IMn02dDUN/H/mqn9jvptWpsunQkxp5gq0Bf+Ud8= X-Google-Smtp-Source: APBJJlHn2cALGMJj+vaLK170y/j51LU904mjkvGNgMiUUY1kst+7N0VCOQe1lYxV9q8X+a4Peda5rPz6Rh/rJjy6vuQ= X-Received: by 2002:a2e:b0c6:0:b0:2b9:e0bf:fc58 with SMTP id g6-20020a2eb0c6000000b002b9e0bffc58mr2590486ljl.13.1690901482275; Tue, 01 Aug 2023 07:51:22 -0700 (PDT) MIME-Version: 1.0 References: <89a415b86d5421941e4281ba5bf6288934078624.camel@j-davis.com> <573014.1686375211@sss.pgh.pa.us> <20230612170510.GA201972@gust.leadboat.com> <20230613182920.GA259321@gust.leadboat.com> <1799839.1686687804@sss.pgh.pa.us> <4df537f5a0d8c0ceac3eec3809d1144880b8e76d.camel@j-davis.com> <578fb4be80247570e6a05924908765a0b345971e.camel@j-davis.com> <43bbc9f7318057f51552d5986830908cb018dadf.camel@j-davis.com> <1659699.1688086436@sss.pgh.pa.us> In-Reply-To: From: Robert Haas Date: Tue, 1 Aug 2023 10:51:10 -0400 Message-ID: Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations. To: Jeff Davis Cc: Joe Conway , Tom Lane , Noah Misch , "pgsql-hackers@postgresql.org" , Nathan Bossart Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jul 31, 2023 at 5:15=E2=80=AFPM Jeff Davis wrot= e: > > ERROR: role "rhaas" should not execute arbitrary code provided by > > role "jconway" > > HINT: If this should be allowed, use the TRUST command to permit it. > > +1, though I'm not sure we need an extensive trust mechanism beyond > what we already have with the SET ROLE privilege. FWIW, I think it would be a good idea. It might not be absolutely mandatory but I think it would be smart. --=20 Robert Haas EDB: http://www.enterprisedb.com