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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cowwoc <cowwoc(at)bbs(dot)darktech(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Date: 2014-12-09 22:03:43
Message-ID: 25623.1418162623@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

cowwoc <cowwoc(at)bbs(dot)darktech(dot)org> 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".

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message cowwoc 2014-12-09 22:13:16 Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Previous Message cowwoc 2014-12-09 21:55:32 Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created