Re: corrupted table postgresql 8.3

On Tue, Mar 6, 2012 at 10:15 AM, Matteo Sgalaberni <sgala@sgala.com> wrote:
> Hi people!
>
> I have a pg 8.3. Today I issued in a database that comand:
> =3D# ALTER TABLE cliente ADD COLUMN pwd_expired boolean DEFAULT FALSE;
> WARNING: =A0unexpected attrdef record found for attr 22 of rel cliente
> WARNING: =A0unexpected attrdef record found for attr 22 of rel cliente
> WARNING: =A0unexpected attrdef record found for attr 22 of rel cliente
> ALTER TABLE
> 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
causes.

http://rhaas.blogspot.com/2012/03/why-is-my-database-corrupted.html

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.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company