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 1q9AY8-0000Nj-Cz for pgsql-committers@arkaria.postgresql.org; Tue, 13 Jun 2023 20:23:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q9AY7-0004A9-9v for pgsql-committers@arkaria.postgresql.org; Tue, 13 Jun 2023 20:23:31 +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 1q9AY7-0004A0-3C for pgsql-committers@lists.postgresql.org; Tue, 13 Jun 2023 20:23:31 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q9AY4-002CB8-LK for pgsql-committers@lists.postgresql.org; Tue, 13 Jun 2023 20:23:30 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 35DKNO4P1799840; Tue, 13 Jun 2023 16:23:24 -0400 From: Tom Lane To: Noah Misch cc: Jeff Davis , pgsql-committers@lists.postgresql.org Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations. In-reply-to: <20230613182920.GA259321@gust.leadboat.com> References: <89a415b86d5421941e4281ba5bf6288934078624.camel@j-davis.com> <573014.1686375211@sss.pgh.pa.us> <20230612170510.GA201972@gust.leadboat.com> <20230613182920.GA259321@gust.leadboat.com> Comments: In-reply-to Noah Misch message dated "Tue, 13 Jun 2023 14:29:20 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1799838.1686687804.1@sss.pgh.pa.us> Date: Tue, 13 Jun 2023 16:23:24 -0400 Message-ID: <1799839.1686687804@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Noah Misch writes: > Best argument for shipping without $SUBJECT: we already have REFERENCES and > TRIGGER privilege that tend to let the grantee hijack the table owner's > account. Adding MAINTAIN to the list, while sad, is defensible. I still > prefer to ship with $SUBJECT, not without. What I'm concerned about is making such a fundamental semantics change post-beta1. It'll basically invalidate any application compatibility testing anybody might have done against beta1. I think this ship has sailed as far as v16 is concerned, although we could reconsider it in v17. Also, I fail to see any connection to the MAINTAIN privilege: the committed-and-reverted patch would break things whether the user was making any use of that privilege or not. Thus, I do not accept the idea that we're fixing something that's new in 16. regards, tom lane