Re: duplicate key value violates unique constraint "pg_class_relname_nsp_index"
От | Adrian Klaver |
---|---|
Тема | Re: duplicate key value violates unique constraint "pg_class_relname_nsp_index" |
Дата | |
Msg-id | 5565C775.3070609@aklaver.com обсуждение исходный текст |
Ответ на | Re: duplicate key value violates unique constraint "pg_class_relname_nsp_index" (Melvin Davidson <melvin6925@gmail.com>) |
Ответы |
Re: duplicate key value violates unique constraint "pg_class_relname_nsp_index"
|
Список | pgsql-general |
On 05/27/2015 06:05 AM, Melvin Davidson wrote: > What this indicates is that someone, or some thing, is trying to create > a table in a schema that already exists. The error you see in that situation is: postgres-2015-05-27 06:25:10.173 PDT-0ERROR: relation "table1" already exists postgres-2015-05-27 06:25:10.173 PDT-0STATEMENT: create table table1 (i int); Best guess is as Pete and Albe said, some user code is directly accessing pg_class or the index has been corrupted. > Here is the structure of pg_class_relname_nsp_index: > CREATE UNIQUE INDEX pg_class_relname_nsp_index ON pg_class USING btree > (relname, relnamespace) > > What you should also see in the error log is a line immediately > following that error which shows you exactly what the conflict is, but > you have not provided that to us. > -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: