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

From Tom Lane
Subject Re: BUG #5950: backend terminating after altering table
Date
Msg-id 23848.1301336139@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #5950: backend terminating after altering table  (Sergey Burladyan <eshkinkot@gmail.com>)
List pgsql-bugs
Sergey Burladyan <eshkinkot@gmail.com> writes:
> 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):

Yeah, I had already come to the conclusion that it was just luck that
HEAD avoids the specific problem.  See
http://archives.postgresql.org/pgsql-hackers/2011-03/msg01673.php

            regards, tom lane

pgsql-bugs by date:

Previous
From: Sergey Burladyan
Date:
Subject: Re: BUG #5950: backend terminating after altering table
Next
From: Robert Haas
Date:
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)