From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Frank Alberto Rodriguez Solana <franknigth(at)gmail(dot)com> |
Cc: | pgsql-novice <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: ERROR on database index |
Date: | 2019-03-28 19:49:51 |
Message-ID: | b8a38dfa059d055041f8a893f8f8a6f905e5f2e9.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Frank Alberto Rodriguez Solana wrote:
> Hi Laurenz, thanks for you reply. I do REINDEX but then the same problem was trigger but with pg_description_o_c_o_index,
>
> [XX002] org.postgresql.util.PSQLException: ERROR: index "pg_description_o_c_o_index" contains unexpected zero page at block
>
> I reindex pg_description and I don't see more problems. The system file type is ext4 and is a cloud server.
>
> But seeing logs I saw other problem in the same server but other database:
> ERROR: invalid page in block 1478644 of relation pg_tblspc/117936/PG_10_201707211/117939/259612
>
> that's makes me wonder if the problem is in the filesystem, but I have 3 cloud servers with the same
> specification and working charge, and each server have an incremental backup with barman.
At this point I would restore a backup, pg_dumpall and restore to a new server.
Data corruption can spread.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Prasad | 2019-04-04 14:48:01 | RAM usage of PostgreSql |
Previous Message | Frank Alberto Rodriguez Solana | 2019-03-28 16:47:25 | Re: ERROR on database index |