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 1kopMV-0007ap-TB for pgsql-hackers@arkaria.postgresql.org; Mon, 14 Dec 2020 15:02:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kopMU-0008Sq-Sq for pgsql-hackers@arkaria.postgresql.org; Mon, 14 Dec 2020 15:02:06 +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 1kopLs-0005Yv-KS for pgsql-hackers@lists.postgresql.org; Mon, 14 Dec 2020 15:01:28 +0000 Received: from mxout2.routing.net ([2a03:2900:1:a::b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kopLm-0003Gq-1W for pgsql-hackers@postgresql.org; Mon, 14 Dec 2020 15:01:28 +0000 Received: from mxbox1.masterlogin.de (unknown [192.168.10.88]) by mxout2.routing.net (Postfix) with ESMTP id 457CB5FD7A; Mon, 14 Dec 2020 15:01:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailerdienst.de; s=20200217; t=1607958079; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=zEI+Tj6bn9jNuDkndcG3UEDFwvN7w1srTs/vS5EDn8A=; b=WOQQnH9E9pcViDbVonEr4ns+2xoOpl7XXX1ugcQ14yLLIim+yfqsjmXX4qM/g1uOzW4EV7 ELze555oeVE7E6bMBG83yE7ARUg9GuOiPUGATMgCCP//4FBt7pLh/NLZxFmZOxUYJjcJpg dvjTKNWREaSp2V/gt6e0kia/rR9XeO8= Received: from remote.index.de (business-90-187-114-221.pool2.vodafone-ip.de [90.187.114.221]) by mxbox1.masterlogin.de (Postfix) with ESMTPSA id A1363402EF; Mon, 14 Dec 2020 15:01:18 +0000 (UTC) Received: from invidia.index-gruppe.local (192.168.3.140) by acedia.index-gruppe.local (192.168.3.121) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1034.26; Mon, 14 Dec 2020 16:01:18 +0100 Received: from acedia.index-gruppe.local (192.168.3.121) by invidia.index-gruppe.local (192.168.3.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1034.26; Mon, 14 Dec 2020 16:01:17 +0100 Received: from acedia.index-gruppe.local ([fe80::ecd1:5d0a:a834:dd56]) by acedia.index-gruppe.local ([fe80::ecd1:5d0a:a834:dd56%5]) with mapi id 15.01.1034.033; Mon, 14 Dec 2020 16:01:17 +0100 From: Arne Roland To: Amit Langote , Tomas Vondra CC: "David G. Johnston" , PostgreSQL-development Subject: Re: a misbehavior of partition row movement (?) Thread-Topic: a misbehavior of partition row movement (?) Thread-Index: AQHWmLNk3TJTUi7wd0y+nolzgVoC06mEPugAgADLzICAAI9GgIAAAx+AgEuIyICAJct6AIAALEm6 Date: Mon, 14 Dec 2020 15:01:17 +0000 Message-ID: <5f16e90450bb407ebdc34804b1d2f7a9@index.de> References: , In-Reply-To: Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.3.145] Content-Type: multipart/alternative; boundary="_000_5f16e90450bb407ebdc34804b1d2f7a9indexde_" MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_5f16e90450bb407ebdc34804b1d2f7a9indexde_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, thanks for looking into this. I haven't yet looked at your patch in detail,= yet I think we should address the general issue here. To me this doesn't s= eem to be a RI-trigger issue, but a more general issue like I mentioned in = the pg-bugs thread https://www.postgresql.org/message-id/b1bfc99296e3472590= 0bcd9689be8420@index.de While I like the idea of making fks work, I'd prefer a solution that fires = the appropriate row trigger for partitioned tables for non RI-cases as well= . Regards Arne --_000_5f16e90450bb407ebdc34804b1d2f7a9indexde_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,


thanks for looking into this. I haven't yet looked at your patch in deta= il, yet I think we should address the general issue here. To me this doesn'= t seem to be a RI-trigger issue, but a more general issue like I mentioned = in the pg-bugs thread https://www.postgresql.org/message-id/b1bfc99296e34725900bcd9689be8420@inde= x.de


While I like the idea of making fks work, I'd prefer a solution that fir= es the appropriate row trigger for partitioned tables for non RI-cases= as well.


Regards

Arne




--_000_5f16e90450bb407ebdc34804b1d2f7a9indexde_--