From: Rui DeSousa <rui.desousa@icloud.com>
To: pavan95 <pavan.postgresdba@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix
Date: Mon, 11 Jun 2018 12:52:49 -0400
Message-ID: <477ADE32-3CCE-4A9A-A286-ADDAB0B4F74B@icloud.com> (raw)
In-Reply-To: <1528723690634-0.post@n3.nabble.com>
References: <1528723690634-0.post@n3.nabble.com>
> 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/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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rui.desousa@icloud.com, pavan.postgresdba@gmail.com
Subject: Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix
In-Reply-To: <477ADE32-3CCE-4A9A-A286-ADDAB0B4F74B@icloud.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox