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 1kcM8r-00012e-Dm for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Nov 2020 05:24:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kcM8q-0007ey-C8 for pgsql-hackers@arkaria.postgresql.org; Tue, 10 Nov 2020 05:24:28 +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 1kcM8q-0007er-5J for pgsql-hackers@lists.postgresql.org; Tue, 10 Nov 2020 05:24:28 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kcM8o-0004Bi-5e for pgsql-hackers@postgresql.org; Tue, 10 Nov 2020 05:24:27 +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 0AA5OL4M2111234; Tue, 10 Nov 2020 00:24:21 -0500 From: Tom Lane To: Andres Freund cc: "Drouvot, Bertrand" , PostgreSQL-development Subject: Re: [BUG]: segfault during update In-reply-to: <20201110051041.m5x3ndtc66bwvvfu@alap3.anarazel.de> References: <1831655.1604855899@sss.pgh.pa.us> <1832746.1604857604@sss.pgh.pa.us> <20201110051041.m5x3ndtc66bwvvfu@alap3.anarazel.de> Comments: In-reply-to Andres Freund message dated "Mon, 09 Nov 2020 21:10:41 -0800" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2111232.1604985861.1@sss.pgh.pa.us> Date: Tue, 10 Nov 2020 00:24:21 -0500 Message-ID: <2111233.1604985861@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Andres Freund writes: > On 2020-11-08 12:46:44 -0500, Tom Lane wrote: >> In v12 we end up using the junkfilter's output >> slot, which does not have a sufficiently accurate tupdesc to deal with >> an on-disk tuple rather than one constructed by the executor. > I really wonder if we ought to redesign the column default logic to > really be a property of the Attr, instead of the constraint stuff it is > now. Yeah, I don't much like treating it as a constraint either. Not quite sure that it's worth the work to move it somewhere else, though. > Is it worth adding Bertrand's testcase to the regression suite in some > form? I did add an equivalent test case. regards, tom lane