Skip site navigation (1) Skip section navigation (2)

Re: BUG #5950: backend terminating after altering table

From: Sergey Burladyan <eshkinkot(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "alex" <perepelica(dot)alex(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5950: backend terminating after altering table
Date: 2011-03-28 18:04:25
Message-ID: 87wrjj86l2.fsf@home.progtech.ru (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> "alex" <perepelica(dot)alex(at)gmail(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2011-03-28 18:15:39
Subject: Re: BUG #5950: backend terminating after altering table
Previous:From: Rainer PruyDate: 2011-03-28 14:31:35
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group