Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihZXW-0004tH-QS for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Dec 2019 13:38:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ihZXT-0007bQ-OH for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Dec 2019 13:38:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihZXT-0007bJ-Fi for pgsql-hackers@lists.postgresql.org; Wed, 18 Dec 2019 13:38:55 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ihZXP-0000Nq-P9 for pgsql-hackers@lists.postgresql.org; Wed, 18 Dec 2019 13:38:54 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xBIDckPV028161; Wed, 18 Dec 2019 08:38:46 -0500 From: Tom Lane To: Amit Langote cc: PostgreSQL Hackers Subject: Re: unsupportable composite type partition keys In-reply-to: References: <5361.1576602769@sss.pgh.pa.us> Comments: In-reply-to Amit Langote message dated "Wed, 18 Dec 2019 15:13:48 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <28159.1576676326.1@sss.pgh.pa.us> Date: Wed, 18 Dec 2019 08:38:46 -0500 Message-ID: <28160.1576676326@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Amit Langote writes: > On Wed, Dec 18, 2019 at 2:12 AM Tom Lane wrote: >> Hm. Seems like the restrictions here ought to be just about the same >> as on index columns, no? > We also need to disallow self-referencing composite type in the case > of partitioning, because otherwise it leads to infinite recursion > shown in my first email. My point is basically that CheckAttributeType already covers that issue, as well as a lot of others. So why isn't the partitioning code using it? regards, tom lane