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

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: cowwoc <cowwoc(at)bbs(dot)darktech(dot)org>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Date: 2015-01-12 18:19:16
Message-ID: 20150112181916.GG2092@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2014-12-09 17:25:43 -0500, Tom Lane wrote:
> cowwoc <cowwoc(at)bbs(dot)darktech(dot)org> writes:
> > Tom Lane-2 wrote
> >> 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:
>
> If it was non-reproducible, you really should have mentioned that to start
> with. That fact changes the likely causes significantly. Now I'm
> wondering about flaky hardware, for example.

cowwoc just talked about this on irc, and the explanation very likely is
that the extension commands are run in parallel on several
connections.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message cowwoc 2015-01-12 20:58:30 Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Previous Message Johnny B 2015-01-12 16:52:43 Re: BUG #12523: postgresql-libs-8.4.22-i386 missing