per suggestion from Rene Gollent.
* Portions Copyright (c) 1994, Regents of the University of California
*
* IDENTIFICATION
- * $PostgreSQL: pgsql/src/backend/utils/sort/tuplesort.c,v 1.78 2007/09/01 18:47:39 tgl Exp $
+ * $PostgreSQL: pgsql/src/backend/utils/sort/tuplesort.c,v 1.79 2007/10/29 21:31:28 tgl Exp $
*
*-------------------------------------------------------------------------
*/
if (state->enforceUnique && !equal_hasnull && tuple1 != tuple2)
ereport(ERROR,
(errcode(ERRCODE_UNIQUE_VIOLATION),
- errmsg("could not create unique index"),
+ errmsg("could not create unique index \"%s\"",
+ RelationGetRelationName(state->indexRel)),
errdetail("Table contains duplicated values.")));
/*
-- add a unique constraint (fails)
alter table atacc1 add constraint atacc_test1 unique (test);
NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index "atacc_test1" for table "atacc1"
-ERROR: could not create unique index
+ERROR: could not create unique index "atacc_test1"
DETAIL: Table contains duplicated values.
insert into atacc1 (test) values (3);
drop table atacc1;
-- add a primary key (fails)
alter table atacc1 add constraint atacc_test1 primary key (test);
NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "atacc_test1" for table "atacc1"
-ERROR: could not create unique index
+ERROR: could not create unique index "atacc_test1"
DETAIL: Table contains duplicated values.
insert into atacc1 (test) values (3);
drop table atacc1;
ERROR: duplicate key value violates unique constraint "concur_index2"
-- check if constraint is enforced properly at build time
CREATE UNIQUE INDEX CONCURRENTLY concur_index3 ON concur_heap(f2);
-ERROR: could not create unique index
+ERROR: could not create unique index "concur_index3"
DETAIL: Table contains duplicated values.
-- test that expression indexes and partial indexes work concurrently
CREATE INDEX CONCURRENTLY concur_index4 on concur_heap(f2) WHERE f1='a';