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

Re: BUG #5950: backend terminating after altering table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sergey Burladyan <eshkinkot(at)gmail(dot)com>
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:15:39
Message-ID: 23848.1301336139@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Sergey Burladyan <eshkinkot(at)gmail(dot)com> writes:
> 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):

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

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2011-03-28 18:20:55
Subject: Re: BUG #5946: Long exclusive lock taken by vacuum (not full)
Previous:From: Sergey BurladyanDate: 2011-03-28 18:04:25
Subject: Re: BUG #5950: backend terminating after altering table

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