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 1pFiD5-0005pd-Ku for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Jan 2023 21:00:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pFiD4-0001WT-B3 for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Jan 2023 21:00:34 +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 1pFiAq-0004IO-Rr for pgsql-hackers@lists.postgresql.org; Wed, 11 Jan 2023 20:58:16 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pFiAo-0002ze-UM for pgsql-hackers@lists.postgresql.org; Wed, 11 Jan 2023 20:58:16 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 30BKwBuL667768; Wed, 11 Jan 2023 15:58:11 -0500 From: Tom Lane To: Amit Langote cc: pgsql-hackers@lists.postgresql.org, Peter Eisentraut Subject: Re: ATTACH PARTITION seems to ignore column generation status In-reply-to: References: <2793383.1672944799@sss.pgh.pa.us> <3016779.1673026372@sss.pgh.pa.us> <44978.1673300465@sss.pgh.pa.us> <191819.1673318283@sss.pgh.pa.us> <378312.1673388786@sss.pgh.pa.us> Comments: In-reply-to Amit Langote message dated "Wed, 11 Jan 2023 12:43:50 +0900" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <667766.1673470691.1@sss.pgh.pa.us> Date: Wed, 11 Jan 2023 15:58:11 -0500 Message-ID: <667767.1673470691@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Amit Langote writes: > I've updated your disallow-generated-child-columns-2.patch to do this, > and have also merged the delta post that I had attached with my last > email, whose contents you sound to agree with. Pushed with some further work to improve the handling of multiple- inheritance cases. We still need to insist that all or none of the parent columns are generated, but we don't have to require their generation expressions to be alike: that can be resolved by letting the child table override the expression, much as we've long done for plain default expressions. (This did need some work in pg_dump after all.) I'm pretty happy with where this turned out. regards, tom lane