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 1m6crW-0007sU-MF for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Jul 2021 17:51:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m6crV-0006xI-99 for pgsql-hackers@arkaria.postgresql.org; Thu, 22 Jul 2021 17:51:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m6crV-0006td-1K for pgsql-hackers@lists.postgresql.org; Thu, 22 Jul 2021 17:51:57 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m6crT-0001ZK-00 for pgsql-hackers@lists.postgresql.org; Thu, 22 Jul 2021 17:51:56 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 1525F5C00D4; Thu, 22 Jul 2021 13:51:54 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 22 Jul 2021 13:51:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=XIpa09T91iaNJUrCZXnm5iGI3U5iewc6kX5ggYCsaXM=; b=u8lhORbu mXTfmo6QFsEqaJMcJotMmn+EFotFm+v2vyvdw7SvgddOg0nWLqntYhoOT13fpAEo ly9hFKSBXpik7jEk8qm5Ei72RNlj521Kuw3ybrK8gA2Z7qeNEaKHVjSC3mHph47C 0pIIqm0zWWexTiBuo5slV6nH35Hx3JPVspX9N2ziaTrt6ychIN4zcICVRtDFCzyl f+EmzIUURyhz150GfcoIRElcXgdWAHiv5nBlVg7YdVEQ6rm8PKxzqAsc741so0we 5xI+8K0hDYUFNW848Ztk8Lq/9y2ThO6wScWRv4pJCJeKZIkLRjGBT6cOIjAeYRI5 Q+TbD2fudkKwVA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrfeeigddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedujeevjeffjeevuddutedvkeeiueeitddvieelfeekveej udefgeeuvdejhfeuleenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 22 Jul 2021 13:51:52 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 17F592A09B6; Thu, 22 Jul 2021 13:51:50 -0400 (-04) Date: Thu, 22 Jul 2021 13:51:50 -0400 From: Alvaro Herrera To: Arne Roland Cc: vignesh C , Zhihong Yu , Pg Hackers Subject: Re: Rename of triggers for partitioned tables Message-ID: <202107221751.adgv73algddv@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <85343944ff5f43d8b30fdd258a97d85b@index.de> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Jul-22, Arne Roland wrote: > alter table middle disable trigger b; > creates the same kind of inconsistency > alter trigger b on middle rename to something; > does. > With other words: enableing/disabling non-topmost triggers should be forbidden as well. I'm not so sure about that ... I think enabling/disabling triggers on individual partitions is a valid use case. Renaming them, not so much. -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/ "No necesitamos banderas No reconocemos fronteras" (Jorge González)