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

Re: corrupted table postgresql 8.3

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Matteo Sgalaberni <sgala(at)sgala(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: corrupted table postgresql 8.3
Date: 2012-04-09 14:18:28
Message-ID: (view raw or whole thread)
Lists: pgsql-bugspgsql-general
On Tue, Mar 6, 2012 at 10:15 AM, Matteo Sgalaberni <sgala(at)sgala(dot)com> wrote:
> Hi people!
> I have a pg 8.3. Today I issued in a database that comand:
> =# ALTER TABLE cliente ADD COLUMN pwd_expired boolean DEFAULT FALSE;
> WARNING:  unexpected attrdef record found for attr 22 of rel cliente
> WARNING:  unexpected attrdef record found for attr 22 of rel cliente
> WARNING:  unexpected attrdef record found for attr 22 of rel cliente
> Time: 1184.404 ms
> After that the table was empty.

I suppose it's a bit late to be answering this now, but it sounds like
you've got a corrupted database, which is something that can have many

Generally, the way people handle problems like the one you have in
practice is to do enough surgery on the catalogs to make pg_dump work,
and then restore into a freshly created database.

Robert Haas
The Enterprise PostgreSQL Company

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2012-04-09 14:20:59
Subject: Re: BUG #6464: Installer (postgresql-9.1.2-1-windows-x64.exe) doesn't work
Previous:From: Robert HaasDate: 2012-04-09 14:15:27
Subject: Re: BUG #6521: cannot make connection due to "getsockname() failed: Invalid argument"

pgsql-general by date

Next:From: Bret SternDate: 2012-04-09 14:35:26
Subject: Re: Regarding NOTIFY
Previous:From: leaf_yxjDate: 2012-04-09 13:52:36
Subject: Re: Questions of the privileges to use the pg_cancel_backend and pg_terminate_backend function. Thanks.

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