From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Health checks after machine crash? |
Date: | 2018-04-23 19:09:33 |
Message-ID: | 14e7c714-f747-05be-9a80-4066b607a6a2@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On 04/23/2018 12:58 PM, Jerry Sievers wrote:
> Ron <ronljohnsonjr(at)gmail(dot)com> writes:
>
>> Hi,
>>
>> v8.4 (Yes, it's archaic. Upgrade plan is in progress.)
> Please do! :-)
>
>> What queries should I run against the catalog tables to see whether or
>> not the cluster is healthy after reboot?
> Is the cluster confi'd to be at risk of corruption after crash.. such as
> full_page_write=off, fsync=off?
#full_page_writes = on
fsync = on
> Do your logs show any obvious sign of corruption, bad blocks etc?
Nothing I've notived.
> You may have little to worry about since Pg is very crash tolerant even
> old versions 8.4 and prior.
>
> I'd try vacuum and analyze whole cluster plus dumpall >/dev/null and
> check for errors there too. Any sort of corruption likely to cause
> application problems likely to show up in so doing.
Will do.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Sushil Shirodkar | 2018-04-26 15:31:01 | vacuumdb causes memory drain. |
Previous Message | Jerry Sievers | 2018-04-23 17:58:31 | Re: Health checks after machine crash? |