From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org, Andrew Dunstan <andrew@dunslane.net>
Subject: Re: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default
Date: Thu, 10 Jun 2021 18:10:29 -0400
Message-ID: <1806408.1623363029@sss.pgh.pa.us> (raw)
In-Reply-To: <17056-4f6f7243d322be6b@postgresql.org>
References: <17056-4f6f7243d322be6b@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com, andrew@dunslane.net
Subject: Re: BUG #17056: Segmentation fault on altering the type of the foreign table column with a default
In-Reply-To: <1806408.1623363029@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox