Re: BUG #5338: PG_DUMP fails due to invalid adnum value

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Toni Helenius <Toni(dot)Helenius(at)syncrontech(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5338: PG_DUMP fails due to invalid adnum value
Date: 2010-02-24 15:54:46
Message-ID: 7761.1267026886@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Toni Helenius <Toni(dot)Helenius(at)syncrontech(dot)com> writes:
> I actually managed to trace this so that I can reproduce the crashing simply with an empty table created as in attachment. If I delete the table, everything is fine. The table can be empty and pg_dump still crashes. This is really weird...

Works for me --- I ran that script and could dump the table no problem.

I'm still thinking this is corruption in your copy of pg_attrdef; maybe
its indexes are messed up. Try reindexing it.

BTW, you forgot to attach the pg_attrdef query output ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2010-02-24 16:00:49 Re: BUG #4921: ltree @> ltree[] operator shouldn't fail if ltree[] is empty
Previous Message Lou Picciano 2010-02-24 15:51:19 PostgreSQL-9.0alpha: jade required?