Re: Postgresql 9.3 - problem after crash server

I am pretty sure the database is corrupted.

Unfortunately, i am not able to help you more. Sorry

The only advices I have are :
Invest in a battery between power and server (UPS)
Have backups (logical and physical) more recent

Maybe community will able to help you...
Good luck

Le jeu. 2 août 2018 à 18:12, Forall <forall(at)stalowka(dot)info> a écrit :

> Yes, I connected to the database e200 but still select results nothing
> select * from pg_class where oid=12685;
>
> I think database is corrupted...
>
>
>
> W dniu 2018-08-02 o 16:33, Thomas Poty pisze:
>
> Are you connected to the database "e200"?
>
> Le jeu. 2 août 2018 à 16:05, Albert <forall(at)stalowka(dot)info> a écrit :
>
>> W dniu 02.08.2018 o 15:52, Thomas Poty pisze:
>>
>> 157934 is the oid of your database
>> if you run => select oid, datname from pg_database where oid =157934;
>> The result should be oid = 157934 and datname = e200
>>
>> select oid, datname from pg_database where oid =157934;
>> oid | datname
>> --------+---------
>> 157934 | e200
>> (1 row)
>>
>> 12685 is the oid of your relation
>> if you run => select * from pg_class where oid=12685;
>> it will give you information about the relation
>>
>> select * from pg_class where oid=12685;
>> relname | relnamespace | reltype | reloftype | relowner | relam |
>> relfilenode | reltablespace | relpages | reltuples | relallvisible |
>> reltoastrelid | reltoastidxid | relhasindex | relisshared | relpersistence
>> | relkind | relnatts | relchecks | relhasoids | relhaspkey |
>> relhasrules | relhastriggers | relhassubclass | relispopulated |
>> relfrozenxid | relminmxid | relacl | reloptions
>>
>> ---------+--------------+---------+-----------+----------+-------+-------------+---------------+----------+-----------+---------------+---------------+---------------+-------------+-------------+----------------+---------+----------+-----------+------------+------------+-
>>
>> ------------+----------------+----------------+----------------+--------------+------------+--------+------------
>> (0 rows)
>>
>> reindexdb -d e200
>> NOTICE: table "pg_catalog.pg_class" was reindexed
>> reindexdb: reindexing of database "e200" failed: ERROR: invalid page in
>> block 101 of relation base/157934/12685
>>
>> I still have that error when I run reindexdb -d e200...
>>
>>
>>
>>
>>
>