From: | Thomas Poty <thomas(dot)poty(at)gmail(dot)com> |
---|---|
To: | forall(at)stalowka(dot)info |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Postgresql 9.3 - problem after crash server |
Date: | 2018-08-02 13:19:17 |
Message-ID: | CAN_ctngWfM3LAYYvL4aJb0Nd-C+qj_oCHxuQssXFt3p=4+8iiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I don't know if it will help you but you could try this:
Identify " base/157934/12685"
If It is an index than drop this index and rebuild it
if It is a table than drop all indexes and rebuild them all
Le jeu. 2 août 2018 à 13:32, For(at)ll <forall(at)stalowka(dot)info> a écrit :
> Hi,
>
> I have problem with postgresql-9.3 in our clients. They suddenly lost
> power connection and all servers halt.. I repiar xfs filesystem on
> CentOS7 postgresql partition. Now when I want run reindex database I
> receive error:
>
> reindexdb -d ex200
> NOTICE: table "pg_catalog.pg_class" was reindexed
> reindexdb: reindexing of database "ex200" failed: ERROR: invalid page
> in block 101 of relation base/157934/12685
>
> I want to try run dump and save database on plaintext but when I start
> pg_dump it's hang...
>
> pg_dump -a -v -d ex200 > ex200.sql
> pg_dump: last built-in OID is 16383
> pg_dump: reading extensions
> pg_dump: identifying extension members
> pg_dump: reading schemas
> pg_dump: reading user-defined tables
> pg_dump: reading user-defined functions
>
> Any ideas what can I do.. Client told me they have a backup from 2
> montgs ago....
>
>
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Poty | 2018-08-02 13:52:43 | Re: Postgresql 9.3 - problem after crash server |
Previous Message | For@ll | 2018-08-02 11:32:01 | Postgresql 9.3 - problem after crash server |