On Mon, Jan 23, 2012 at 3:04 PM, Vik Reykja <vikreykja(at)gmail(dot)com> wrote:
> On Mon, Jan 23, 2012 at 11:25, Marc Balmer <marc(at)msys(dot)ch> wrote:
>> Am 22.01.12 14:22, schrieb Giuseppe Sucameli:
>> > test=> create table lx (i int);
>> > CREATE TABLE
>> > test=> alter table lx add xmin int;
>> > ERROR: column "xmin" of relation "lx" already exists.
>> That is not a bug, but a feature.
> I see it as a message bug. Why wouldn't ALTER TABLE also tell us that xmin
> is a system column? It makes things much more clear for newbies who don't
> see the column yet are told it exists if they're also told it's a system
I agree with Vik, the CREATE TABLE tells "xmin" is a system column,
why wouldn't ALTER TABLE do the same?
This would be a feature if CREATE TABLE didn't tell us that
xmin is a system column, otherwise is a bug.
> I would try to cook up a patch but I have no skills :-(
I'm going to write a patch to fix this problem.
In response to
pgsql-hackers by date
|Next:||From: Robert Haas||Date: 2012-01-24 13:58:58|
|Subject: Re: basic pgbench runs with various performance-related patches|
|Previous:||From: Heikki Linnakangas||Date: 2012-01-24 12:38:04|
|Subject: Re: Client Messages|
pgsql-bugs by date
|Next:||From: Giuseppe Sucameli||Date: 2012-01-24 14:10:48|
|Subject: Different error messages executing CREATE TABLE or ALTER TABLE to
create a column "xmin"|
|Previous:||From: Andrew Alcheyev||Date: 2012-01-24 12:59:10|
|Subject: Re: FreeBSD 9.0/amd64, PostgreSQL 9.1.2, pgbouncer 1.4.2: segmentation fault|