Re: Fwd: Postgresql Data corruption

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Tulqin Navruzov <tulqin(dot)navruzov(at)finnetlimited(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Fwd: Postgresql Data corruption
Date: 2020-01-15 02:53:30
Message-ID: 20200115025330.GE2243@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jan 14, 2020 at 02:34:04PM -0800, Adrian Klaver wrote:
> On 1/14/20 12:44 PM, Tulqin Navruzov wrote:
>> but can logged in with another user and trying to select from some
>> tables , showing this message :
>>
>> ERROR:  catalog is missing 11 attribute(s) for relid 113971
>>
>> Could you help us to solve this problem? or could you give contact who
>> can help with this?
>
> Do you have space to back up the $DATADIR or do you have a recent backup?
>
> Asking because that would be helpful before you try the below.
>
> I would take a look at:
> https://www.postgresql.org/docs/12/sql-reindex.html

That's a bad data corruption pattern, and rolling in a backup is
recommended (make sure that they are actually safe to use!). A
REINDEX should help you to retrieve data and move it somewhere else if
you don't have a backup, but nothing more as there is no guarantee
that other parts of the system are not broken. As others have already
pointed out, take the time necessary to read that:
https://wiki.postgresql.org/wiki/Corruption

But first, you should take three, slow, deep breaths. Rushing can
only make things worse.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message yotsunaga.naoki@fujitsu.com 2020-01-15 02:58:45 Lock acquisition for partition table when setting generic plan
Previous Message James Sewell 2020-01-14 23:42:06 Lock leaking out of Transaction?