| From: | Holger Jakobs <holger(at)jakobs(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org, Dan Smith <j(dot)daniel(dot)smith1(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Corruption issue |
| Date: | 2023-09-23 09:34:24 |
| Message-ID: | 1D460E80-E3B1-493D-9801-A34DD9657CA2@jakobs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
chkdsk is a Windows program, but the original poster wrote her is using Linux.
So, badblocks could be the appropriate program.
Am 22. September 2023 18:55:14 MESZ schrieb Dan Smith <j(dot)daniel(dot)smith1(at)gmail(dot)com>:
>On Fri, Sep 22, 2023, 12:48 PM OS DB2 <opensourcedb2(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> In one of the our production database when we are trying to fetch the
>> records from one of the table, we are getting below error.
>>
>> *Compressed data is corrupted*
>>
>> Os - linux
>> Postgresql version - 9.5
>>
>> We have restored data somehow using secondary node but still please let me
>> know how we can find out the root cause and avoid such scenarios in future.
>>
>> Regards,
>> Nikhil
>>
>
>
>Recommend running chkdsk and upgrade the cluster (9.5 is EOL).
>
>
>Best regards,
>
>Dan Smith
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Gibbins | 2023-09-23 10:53:08 | Segmentation fault when running queries in sequence |
| Previous Message | Dan Smith | 2023-09-22 16:55:14 | Re: Corruption issue |