Re: PostgreSQL 'Corruption & Fragmentation' detection andresolution/fix - Mailing list pgsql-admin

From Rui DeSousa
Subject Re: PostgreSQL 'Corruption & Fragmentation' detection andresolution/fix
Date
Msg-id 477ADE32-3CCE-4A9A-A286-ADDAB0B4F74B@icloud.com
Whole thread Raw
In response to Re: PostgreSQL 'Corruption & Fragmentation' detection andresolution/fix  (pavan95 <pavan.postgresdba@gmail.com>)
Responses Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix  (Pavan Teja <pavan.postgresdba@gmail.com>)
List pgsql-admin
> On Jun 11, 2018, at 9:28 AM, pavan95 <pavan.postgresdba@gmail.com> wrote:
>
> I'm searching a way to detect postgresql corruption on a daily basis. Please
> provide me
>

If you haven’t already (show data_checksums); I would recommend turning on data checksums to allow Postgres to detect
i/odata corruption issues.   

If it’s not enabled then you’ll have to reinit your database:  initdb —data-checksums …

I would be very concerned why you feel the need to check for corruption and would question your platform.  The only
timeI’ve seen corruption was due to a disk subsystem problem which data-checksums should help flush out for you or a
Postgresbug which would normally gets bubbled up via the application and/or the logs. 

Make sure you have good backups; there really is no script that going to solve a faulty disk subsystem or other
disaster.

pgsql-admin by date:

Previous
From: Rui DeSousa
Date:
Subject: Re: pg_stat_activity
Next
From: Pavan Teja
Date:
Subject: Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix