From: | Fabio Pardi <f(dot)pardi(at)portavita(dot)eu> |
---|---|
To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix |
Date: | 2018-06-11 13:36:54 |
Message-ID: | 1df82d63-3eeb-345e-6c58-19f05470247f@portavita.eu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Pavan,
Whatover my experience turned out to be (incidentally) useful is a vacuum over the whole database(s). I have one that runs every night and when corruption happens, you will noticeit because vacuum will die, hopefully noticing you.
As per the fix, I m not sure. I think that if you find curruption, you should first understand what is corrupted. If you are lucky, is an index, and a recreation will fix it for you. But if the corruption happens on real data, then the problem must be approached in some other way(s).
regards,
fabio pardi
On 11/06/18 15:28, pavan95 wrote:
> Hi all,
>
> I'm searching a way to detect postgresql corruption on a daily basis. Please
> provide me
>
> 1) a script which detects the corruption in postgres database/instance,
>
> 2) and the remedy steps to fix the issue
>
> Searched in lot of links and blogs but unable to find a concrete solution
>
> And also it will be a very great help to me if I can get in the same way
> for fragmentation.
>
> Please help me regarding this, since it has been a very long time working on
> this.
>
> Thanks in advance.
>
>
> Regards,
> Pavan
>
>
>
> --
> Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2018-06-11 13:37:36 | pg_stat_activity |
Previous Message | pavan95 | 2018-06-11 13:28:10 | Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix |