Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error - Mailing list pgsql-admin

From Tom Lane
Subject Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error
Date
Msg-id 2325374.1771476717@sss.pgh.pa.us
Whole thread Raw
In response to Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error  (Ed Sabol <edwardjsabol@gmail.com>)
Responses Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error
List pgsql-admin
Ed Sabol <edwardjsabol@gmail.com> writes:
> Using PostgreSQL 15.16, I have some SQL for creating a materialized view that's inside a larger transaction which
randomlyemits the following error: 
> ERROR:  duplicate key value violates unique constraint "pg_type_typname_nsp_index"
> DETAIL:  Key (typname, typnamespace)=(largetable, 20488) already exists.

Huh.  Does it always mention 20488?

> I've tried the following queries to try to figure out what typnamespace = 20488 refers to:

> SELECT nspname FROM pg_namespace WHERE oid = 20488;
> SELECT count(*) FROM pg_catalog.pg_type WHERE typname = 'targetable' AND typnamespace = 20488;

> Neither query provides any useful information.

What do you mean by "any useful information", exactly?  Do these show
that there is no pg_namespace row with oid = 20488?

If that is the case, I'd bet on index corruption in the indexes of
pg_type and/or pg_namespace.  REINDEX might help.

            regards, tom lane



pgsql-admin by date:

Previous
From: Ed Sabol
Date:
Subject: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error
Next
From: "Edward J. Sabol"
Date:
Subject: Re: Duplicate key value violates unique constraint "pg_type_typname_nsp_index" error