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 1lrSsn-0004tR-5L for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Jun 2021 22:10:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lrSsm-0001Q5-45 for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Jun 2021 22:10:36 +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 1lrSsl-0001Px-Tq for pgsql-bugs@lists.postgresql.org; Thu, 10 Jun 2021 22:10:35 +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 1lrSsj-0007Bj-Ua for pgsql-bugs@lists.postgresql.org; Thu, 10 Jun 2021 22:10:35 +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 15AMATpg1806409; Thu, 10 Jun 2021 18:10:29 -0400 From: Tom Lane To: exclusion@gmail.com cc: pgsql-bugs@lists.postgresql.org, Andrew Dunstan Subject: Re: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default In-reply-to: <17056-4f6f7243d322be6b@postgresql.org> References: <17056-4f6f7243d322be6b@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 10 Jun 2021 20:00:01 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1806407.1623363029.1@sss.pgh.pa.us> Date: Thu, 10 Jun 2021 18:10:29 -0400 Message-ID: <1806408.1623363029@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > CREATE FOREIGN DATA WRAPPER dummy; > CREATE SERVER s0 FOREIGN DATA WRAPPER dummy; > CREATE FOREIGN TABLE ft1 (c1 integer NOT NULL) SERVER s0; > ALTER FOREIGN TABLE ft1 ADD COLUMN c8 integer DEFAULT 0; > ALTER FOREIGN TABLE ft1 ALTER COLUMN c8 TYPE char(10); Hmm. The equivalent DDL on a plain table works fine, but this is crashing in the code that manipulates attmissingval. I suspect some confusion about whether a foreign table column should even *have* attmissingval. Andrew, any thoughts? regards, tom lane