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:25:43 |
Message-ID: | 26324.1418163943@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:
> 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.
> extname, extowner, extnamespace, extrelocatable, extversion, extconfig,
> extcondition
> "plpgsql";10;11;f;"1.0";"";""
> "hstore";13288111;2200;t;"1.2";"";""
> Is that "reasonable-looking data"?
Yeah, although that OID for the owning role of hstore seems pretty large.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | cowwoc | 2014-12-09 22:41:04 | Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created |
Previous Message | cowwoc | 2014-12-09 22:13:16 | Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created |