Collected from the PG bugs email list.
|OS||Docker (Debian 12.0-2.pgdg100+1) on OSX|
|Reported by||Ariel Mashraki|
Body of first available message related to this bug follows.
The following bug has been logged on the website: Bug reference: 16087 Logged by: Ariel Mashraki Email address: (redacted) PostgreSQL version: 12.0 Operating system: Docker (Debian 12.0-2.pgdg100+1) on OSX Description: Running ALTER TABLE with both ALTER COLUMN and ADD COLUMN causes a database segfault. It happens constantly on version 12 and doesn't reproduce on version 11 and 10. Attaching here a set of commands (and their output) to help reproducing the issue ($ means start of a command). $ create table "users" (id bigint not null generated by default as identity, age int not null, primary key(id)); $ insert into users (age) values(1); $ alter table "users" alter column "age" type bigint, add column "nickname" text; Command output: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempting reset: Failed. Database logs: 2019-10-29 15:08:25.143 UTC  LOG: server process (PID 1747) was terminated by signal 11: Segmentation fault 2019-10-29 15:08:25.143 UTC  DETAIL: Failed process was running: alter table "users" alter column "age" type bigint, add column "nickname" text; 2019-10-29 15:08:25.143 UTC  LOG: terminating any other active server processes 2019-10-29 15:08:25.144 UTC  WARNING: terminating connection because of crash of another server process 2019-10-29 15:08:25.144 UTC  DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. 2019-10-29 15:08:25.144 UTC  HINT: In a moment you should be able to reconnect to the database and repeat your command. 2019-10-29 15:08:25.146 UTC  FATAL: the database system is in recovery mode 2019-10-29 15:08:25.148 UTC  LOG: all server processes terminated; reinitializing 2019-10-29 15:08:25.167 UTC  LOG: database system was interrupted; last known up at 2019-10-29 14:58:57 UTC 2019-10-29 15:08:25.320 UTC  LOG: database system was not properly shut down; automatic recovery in progress 2019-10-29 15:08:25.329 UTC  LOG: redo starts at 0/19835A8 2019-10-29 15:08:25.330 UTC  LOG: invalid record length at 0/199D778: wanted 24, got 0 2019-10-29 15:08:25.330 UTC  LOG: redo done at 0/199D740 2019-10-29 15:08:25.354 UTC  LOG: database system is ready to accept connections
|2019-10-29 15:16:29+00||PG Bug reporting form||BUG #16087: Segmentation fault on ALTER TABLE|
|2019-10-29 15:26:14+00||Tom Lane||Re: BUG #16087: Segmentation fault on ALTER TABLE|