pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
Health checks after machine crash? 3+ messages / 2 participants [nested] [flat]
* Health checks after machine crash? @ 2018-04-23 16:45 Ron <ronljohnsonjr@gmail.com> 0 siblings, 1 reply; 3+ messages in thread From: Ron @ 2018-04-23 16:45 UTC (permalink / raw) To: pgsql-admin Hi, v8.4 (Yes, it's archaic. Upgrade plan is in progress.) What queries should I run against the catalog tables to see whether or not the cluster is healthy after reboot? Thanks -- Angular momentum makes the world go 'round. ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Health checks after machine crash? @ 2018-04-23 17:58 Jerry Sievers <gsievers19@comcast.net> parent: Ron <ronljohnsonjr@gmail.com> 0 siblings, 1 reply; 3+ messages in thread From: Jerry Sievers @ 2018-04-23 17:58 UTC (permalink / raw) To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-admin 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? 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.consulting@comcast.net p: 312.241.7800 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Health checks after machine crash? @ 2018-04-23 19:09 Ron <ronljohnsonjr@gmail.com> parent: Jerry Sievers <gsievers19@comcast.net> 0 siblings, 0 replies; 3+ messages in thread From: Ron @ 2018-04-23 19:09 UTC (permalink / raw) To: pgsql-admin 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. ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2018-04-23 19:09 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2018-04-23 16:45 Health checks after machine crash? Ron <ronljohnsonjr@gmail.com> 2018-04-23 17:58 ` Jerry Sievers <gsievers19@comcast.net> 2018-04-23 19:09 ` Ron <ronljohnsonjr@gmail.com>
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