Re: [BUGS] BUG #5950: backend terminating after altering table

2011-03-28 Thread Tom Lane
"alex" writes: > Such steps: > 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 Thanks for the report. Fixed as per today's discussion (ie, disallow creating a self-referencing rowtype).

Re: [BUGS] BUG #5950: backend terminating after altering table

2011-03-28 Thread Tom Lane
Sergey Burladyan writes: > Tom Lane writes: >> "alex" 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

Re: [BUGS] BUG #5950: backend terminating after altering table

2011-03-28 Thread Sergey Burladyan
Tom Lane writes: > "alex" 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 Segmentat

Re: [BUGS] BUG #5950: backend terminating after altering table

2011-03-25 Thread Tom Lane
"alex" 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: regression=# create table t ( regression(# ); CREATE TABLE regression=# alter table

[BUGS] BUG #5950: backend terminating after altering table

2011-03-25 Thread alex
The following bug has been logged online: Bug reference: 5950 Logged by: alex Email address: perepelica.a...@gmail.com PostgreSQL version: 9.0.3 Operating system: archlinux x86_64 Description:backend terminating after altering table Details: Such steps: 1. create ta