From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | "pgsql-admin\(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Health checks after machine crash? |
Date: | 2018-04-23 17:58:31 |
Message-ID: | 87y3hd4xfc.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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?
Do your logs show any obvious sign of corruption, bad blocks etc?
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.
HTH
> Thanks
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2018-04-23 19:09:33 | Re: Health checks after machine crash? |
Previous Message | Ron | 2018-04-23 16:45:58 | Health checks after machine crash? |