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 1rhXWB-00C0pp-TC for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Mar 2024 16:19:52 +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 1rhXWA-000eY1-7e for pgsql-hackers@arkaria.postgresql.org; Tue, 05 Mar 2024 16:19:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhXW8-000eXs-Ln for pgsql-hackers@lists.postgresql.org; Tue, 05 Mar 2024 16:19:50 +0000 Received: from wfhigh3-smtp.messagingengine.com ([64.147.123.154]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhXW0-002zhA-LB for pgsql-hackers@lists.postgresql.org; Tue, 05 Mar 2024 16:19:47 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailfhigh.west.internal (Postfix) with ESMTP id 479F318000D3; Tue, 5 Mar 2024 11:19:39 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 05 Mar 2024 11:19:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1709655578; x= 1709741978; bh=CqF+dbtnvUQjmf9Sc0WojrJvUS9m5zGkdsWS/Rs6E/0=; b=e sq980QcnYDpdoLmWgDd6zn5FzJKCHogw/ycnYNsfg21ujt6CSIXnu7zRaSpXLQS1 L3PvmETHqJ7FrTDBQBeHQSSmTy7AebikQCv/rDiX3qS13bLtpsdcsQBaO3D2q3nf XrJZNqAkhyFYJJPp4e7hxYKre+519vZMkUTv486Ia68eRcewKVIRqhEzPYciFQaj DDD/GgnXUmbCwkaa5ZgrFsYQAxQaIg1yFeN+KCBxymCLPi2OvAyIppx+echpSN0i bqHRBgUKrSxI3jxBVTsrFeEYBALx2ltiPTpG5NlmjbRqRyW1wmUK3d1WU9ldSYAi wiFkARcxKf8SS5HvKCUeg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrheelgdekfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeejkeff gfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 5 Mar 2024 11:19:38 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1709655575; bh=dgPD9fanqk7rm41I78rf+XML3luDnXHFEpnumvYhAwU=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=JCGRa+aFUojhlRT4JTCXZczOAgJty7Vn4TPlWf2R2P59jpmlLdB2Ecyd5cCznkZg8 WmwNMKTeeIZjGNOe93N0WcCMCysr13lvSqsB8d6I9nwcsO+X1nFBDB6OejCxleSGDT F520Pd/1sMXtJmhskHnApSxriN33JsdjvgTTQvbVaWtrQd7fgPKnuUPi1i61aRVN7K yseTZtzeyjDioJx5YRhRzx29ijZv4+iqYJo1GHfCN6YrX6OMedP1Xil/fse8o3jTCa eVMKfBtwNT7QvTwJUHKvF9HI6sbpFvZZUkqpXCPSrbCU1EO5jcmXIP+sg1VPoI1LWy AxlI2u1C+5nEw== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id BBE22CD5; Tue, 5 Mar 2024 17:19:35 +0100 (CET) Date: Tue, 5 Mar 2024 17:19:35 +0100 From: Alvaro Herrera To: Jeff Davis Cc: pgsql-hackers@lists.postgresql.org Subject: Re: pgsql: Fix search_path to a safe value during maintenance operations. Message-ID: <202403051619.jiuwd3ec4jmi@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-Mar-05, Jeff Davis wrote: > Fix search_path to a safe value during maintenance operations. > > While executing maintenance operations (ANALYZE, CLUSTER, REFRESH > MATERIALIZED VIEW, REINDEX, or VACUUM), set search_path to > 'pg_catalog, pg_temp' to prevent inconsistent behavior. > > Functions that are used for functional indexes, in index expressions, > or in materialized views and depend on a different search path must be > declared with CREATE FUNCTION ... SET search_path='...'. This appears to have upset the sepgsql tests. In buildfarm member rhinoceros there's now a bunch of errors like this ALTER TABLE regtest_table_4 ADD CONSTRAINT regtest_tbl4_con EXCLUDE USING btree (z WITH =); +LOG: SELinux: allowed { search } scontext=unconfined_u:unconfined_r:sepgsql_regtest_superuser_t:s0 tcontext=unconfined_u:object_r:sepgsql_schema_t:s0 tclass=db_schema name="regtest_schema" permissive=0 +LOG: SELinux: allowed { search } scontext=unconfined_u:unconfined_r:sepgsql_regtest_superuser_t:s0 tcontext=system_u:object_r:sepgsql_schema_t:s0 tclass=db_schema name="public" permissive=0 in its ddl.sql test. I suppose this is just the result of the internal change of search_path. Maybe the thing to do is just accept the new output as expected. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ Voy a acabar con todos los humanos / con los humanos yo acabaré voy a acabar con todos (bis) / con todos los humanos acabaré ¡acabaré! (Bender)