Re: Different error messages executing CREATE TABLE or ALTER TABLE to create a column "xmin"

From: Vik Reykja <vikreykja(at)gmail(dot)com>
To: Marc Balmer <marc(at)msys(dot)ch>
Cc: pgsql-bugs(at)postgresql(dot)org, brush(dot)tyler(at)gmail(dot)com
Subject: Re: Different error messages executing CREATE TABLE or ALTER TABLE to create a column "xmin"
Date: 2012-01-23 14:04:27
Message-ID: CALDgxVv2CU4c2kpaRZmDTxfMT=HuyNLRYFGnnH13boPE4cw3Zg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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 (xmin int);
> > ERROR: column name "xmin" conflicts with a system
> > column name
> >
> > 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
column.

I would try to cook up a patch but I have no skills :-(

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2012-01-23 19:40:47 pgcrypto decrypt_iv() issue
Previous Message Marc Balmer 2012-01-23 10:25:01 Re: Different error messages executing CREATE TABLE or ALTER TABLE to create a column "xmin"

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-23 14:25:08 Re: Re: Add minor version to v3 protocol to allow changes without breaking backwards compatibility
Previous Message Robert Haas 2012-01-23 14:00:06 Re: Inline Extension