Skip site navigation (1) Skip section navigation (2)

Re: BUG #4930: Missing attributes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Stefan Kirchev" <stefan(dot)kirchev(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4930: Missing attributes
Date: 2009-07-21 14:24:20
Message-ID: 12309.1248186260@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Stefan Kirchev" <stefan(dot)kirchev(at)gmail(dot)com> writes:
> PostgreSQL version: 8.3.3
> Operating system:   Linux
> Description:        Missing attributes
> Details: 

> One of the tables failed to drop and now it causes pg_dump crash. The table
> was used for temporary storage and the drop query went just fine. Even
> though the table name is still in the pg_tables. Trying to drop it again
> produces the following error:
> pnp=# drop table tmp_msc_data_todiot;
> ERROR:  catalog is missing 33 attribute(s) for relid 1536137

I think this might be another variant of the issue reported at bug
#4929: you've got a pg_class row that somehow got un-marked as deleted.

> Is there any solution on this issue.

Well, first off you need to update to 8.3.4 or later.  What I'd try then
is manually DELETE the pg_class row for that table name, then pg_dump,
initdb, reload.

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Michael JeukDate: 2009-07-21 20:42:28
Subject: BUG #4931: An error occured executing the Microsoft VC++ runtime installer
Previous:From: Mathieu FenniakDate: 2009-07-21 13:16:12
Subject: Re: Bug 4906 -- Left join of subselect incorrect

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group