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 1mhgVk-0004zH-E6 for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Nov 2021 23:14:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mhgVj-0001ZK-6e for pgsql-bugs@arkaria.postgresql.org; Mon, 01 Nov 2021 23:14:39 +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 1mhgVi-0001ZB-Vg for pgsql-bugs@lists.postgresql.org; Mon, 01 Nov 2021 23:14:38 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mhgVf-0007uV-Gi for pgsql-bugs@lists.postgresql.org; Mon, 01 Nov 2021 23:14:38 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7D6335C0200; Mon, 1 Nov 2021 19:14:34 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 01 Nov 2021 19:14:34 -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= fm1; bh=E6qkn8J6ET67VCJ3CdnXKFPTxoWRkfksmkShJP7oZo8=; b=cGaMNaoy /6RkFwA/PqbqVIUplqdebvePd/aJPKCJANYcSsQV3M9db24LTufjhuL+sMV0gWKh FAH2XbQBY1j+tgGurmam/NFsm9yx5Nyw/0alQP/zR7OL8SISKBP8QWsoYgGLQz4x UGllQkAt4etZog+qGbirThHH4ByVXqXogvCetwnBolP12+xNV/aaRsRCNM9En8NX RZrDxOYK8um2WNeA8x5219UNP7AGiXppYPjkbvlXuxFgKHnpZ4uwe5wFN3kovkGi 0o39ZqEZW3lT/KgJYQDkAzwgWxd/johlB7pVHOnyfDE1A3On2Ay/GUZfaiuTf1Jp swGAuTgfi6rerw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddrvdehgedgtdefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpeeuffdvtdffieetveetueetffdvleefvefgfeefteetjeei jefhieegkeeiueetjeenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmpd hhrghtvghsqdhsohhfthifrghrvgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecu rfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprd horhhg X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 1 Nov 2021 19:14:34 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 882362A0804; Mon, 1 Nov 2021 20:14:32 -0300 (-03) Date: Mon, 1 Nov 2021 20:14:32 -0300 From: Alvaro Herrera To: Marcus Gartner Cc: Tom Lane , pgsql-bugs@lists.postgresql.org Subject: Re: BUG #17261: FK ON UPDATE CASCADE can break referential integrity with columns of different types Message-ID: <202111012314.qcqulwshoxfx@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 2021-Nov-01, Marcus Gartner wrote: > I agree with you there. So why is an FK relationship between columns of > different types even allowed? It is useful in other cases, such as varchar or int4/int8. Please don't top-post. -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/ Are you not unsure you want to delete Firefox? [Not unsure] [Not not unsure] [Cancel] http://smylers.hates-software.com/2008/01/03/566e45b2.html