Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created

Tom Lane-2 wrote
> cowwoc <

> cowwoc@.darktech

> > writes:
>> My application invokes:
>>   DROP EXTENSION IF EXISTS hstore CASCADE
>> followed by:
>>   CREATE EXTENSION IF NOT EXISTS hstore SCHEMA public
>> and I get:
>> org.postgresql.util.PSQLException: ERROR: duplicate key value violates
>> unique constraint "pg_extension_name_index"
>>   Detail: Key (extname)=(hstore) already exists.
>
> That's bizarre.  It sounds like there's something corrupt about your
> pg_extension system catalog.  Does "select * from pg_extension" show
> reasonable-looking data?  If so, try "REINDEX TABLE pg_extension".

This error is quite random, so I'll have to try again the next time I run
into it. I get the following output when the database is in a "good" state:

extname, extowner, extnamespace, extrelocatable, extversion, extconfig,
extcondition
"plpgsql";10;11;f;"1.0";"";""
"hstore";13288111;2200;t;"1.2";"";""

Is that "reasonable-looking data"?

Gili



--
View this message in context:
http://postgresql.nabble.com/BUG-6706-pg-upgrade-fails-when-plpgsql-dropped-re-created-tp5714220p5829821.html
Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.