| From: | Andy Marangakis <Andrew(dot)Marangakis(at)colorado(dot)edu> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | runaway processes, data corruption |
| Date: | 2004-10-25 18:48:54 |
| Message-ID: | 417D4A96.2040109@colorado.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi all,
I've encounter a couple of bugaboos recently in a production database I
run (7.3.4 on Solaris 8). One is that killing a query from a client tool
such as dbVisualizer can cause the process on the server to become a
runaway, consuming CPU and causing other processes to go into a
TIME_WAIT state. The other is that a spontaneous reboot of the server
(unknown cause, some hardware/OS wierdness) caused a catastrophic
corruption, requiring rebuild from backup. The error returned was:
PANIC: Invalid page header in block 2462 of 1365344463
I've upgraded to 7.4 in hopes that crash resistance improves. Any other
thoughts on protecting against such occurances in the future? Thanks in
advance.
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Andy Marangakis 303-492-0527
Database Administrator 303-492-4198 fax
Information Technology Services
University of Colorado at Boulder
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Kim | 2004-10-25 19:44:38 | Question: drop database problem |
| Previous Message | Gaetano Mendola | 2004-10-25 17:50:59 | Re: Index relation size |