From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Health checks after machine crash?
Date: Mon, 23 Apr 2018 14:09:33 -0500
Message-ID: <14e7c714-f747-05be-9a80-4066b607a6a2@gmail.com> (raw)
In-Reply-To: <87y3hd4xfc.fsf@jsievers.enova.com>
References: <b1aff4d1-8db0-77bf-3eb9-3f181630cf61@gmail.com>
<87y3hd4xfc.fsf@jsievers.enova.com>
On 04/23/2018 12:58 PM, Jerry Sievers wrote:
> Ron <ronljohnsonjr@gmail.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.
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: ronljohnsonjr@gmail.com
Subject: Re: Health checks after machine crash?
In-Reply-To: <14e7c714-f747-05be-9a80-4066b607a6a2@gmail.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