Thread: how do you determine if you have a healthy database

Confidentiality Note: This e-mail, and any attachment to it, is intended only for the use of the individual(s) or entity named on the e-mail, and may contain confidential or proprietary information (including copyrighted materials). If the reader of is not an authorized recipient, you are hereby notified that reading it or further distributing it (other than to the author or the intended recipient) is prohibited and is potentially an infringement of the rights of the sender or intended recipient. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.   ­­  

On 02/08/2016 04:28 PM, Gregery L. Thompson wrote:
> Two quick questions
>
> 1.How do you determine if you have a healthy database?

I would say start by looking at the database logs. If you are seeing
FATAL and PANIC errors something is not happy.

A lot of this depends on what you consider healthy?

There are conditions within the database, i.e. file corruption and then
there are conditions outside of the database, memory issues, lack of
space, etc. The two can also be connected, where bad memory or hard
drive causes database file corruption.

>
> 2.It needs to be healthy before rebooting correct?

It depends on what is causing the problem. Postgres has a single user
mode that can be started to fix some problems. Also if the database
issue was that it was resource constrained and you fixed that then the
database could be started.

>
> Thanks
>
> Greg
>
> _Greg Thompson_
>
> Sr. Database Administrator
>
> Redflex Traffic Systems, Inc.
>
> 4402 W. Calle Lejos
>
> Glendale, AZ 85310 USA
>
> Ph: +1 (623) 207-2227
>
> Cell: +1 (623) 221-3728
>
> Fx: +1 (623) 207-2050
>
> www.redflex.com
>
> Making A Safer World!
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com