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

pgsql: Be more clear when a new column name collides with a systemcolu

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Be more clear when a new column name collides with a systemcolu
Date: 2012-01-26 17:47:24
Message-ID: E1RqTPw-0000qo-3J@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Be more clear when a new column name collides with a system column name.

We now use the same error message for ALTER TABLE .. ADD COLUMN or
ALTER TABLE .. RENAME COLUMN that we do for CREATE TABLE.  The old
message was accurate, but might be confusing to users not aware of our
system columns.

Vik Reykja, with some changes by me, and further proofreading by Tom Lane

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/2d1371d3ee5cf7e96d16fb503c27e060df9497f7

Modified Files
--------------
src/backend/commands/tablecmds.c          |   64 ++++++++++++++++++++---------
src/test/regress/expected/alter_table.out |    2 +
src/test/regress/expected/errors.out      |    2 +-
src/test/regress/sql/alter_table.sql      |    2 +
4 files changed, 49 insertions(+), 21 deletions(-)

pgsql-committers by date

Next:From: Robert HaasDate: 2012-01-26 19:45:56
Subject: pgsql: Adjust tuplesort.c based on the fact that we never use theOS's
Previous:From: Heikki LinnakangasDate: 2012-01-26 17:09:16
Subject: pgsql: Fix sentence in docs: checkpoints are not done by bgwriteranymo

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