From: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
---|---|
To: | pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix |
Date: | 2018-06-11 16:52:49 |
Message-ID: | 477ADE32-3CCE-4A9A-A286-ADDAB0B4F74B@icloud.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On Jun 11, 2018, at 9:28 AM, pavan95 <pavan(dot)postgresdba(at)gmail(dot)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/o data 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 time I’ve seen corruption was due to a disk subsystem problem which data-checksums should help flush out for you or a Postgres bug 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavan Teja | 2018-06-11 16:58:51 | Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix |
Previous Message | Rui DeSousa | 2018-06-11 16:27:56 | Re: pg_stat_activity |