Re: BUG #5950: backend terminating after altering table - Mailing list pgsql-bugs

From Sergey Burladyan
Subject Re: BUG #5950: backend terminating after altering table
Date
Msg-id 87wrjj86l2.fsf@home.progtech.ru
Whole thread Raw
In response to Re: BUG #5950: backend terminating after altering table  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5950: backend terminating after altering table  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane <tgl@sss.pgh.pa.us> writes:

> "alex" <perepelica.alex@gmail.com> writes:
> > 1. create table t (
> > );
> > 2. alter table t add childs t;
> > 3. alter table t add id serial not null primary key;
> > server closed the connection unexpectedly
>
> Hmm.  This seems to be fixed in HEAD:

Not fully. There are also two cases with Segmentation fault
(from sql.ru forum):
1.
create table t ();
alter table t add childs t;
create table selfchield_new (like t);

2.
create table t ();
alter table t add childs t;
create table selfchield_new as select * from t;

I have segmentation fault with current master 7c7fd882.

--
Sergey Burladyan

pgsql-bugs by date:

Previous
From: Rainer Pruy
Date:
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
Next
From: Tom Lane
Date:
Subject: Re: BUG #5950: backend terminating after altering table