| From: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
|---|---|
| To: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | recovery after segmentation fault |
| Date: | 2009-04-08 14:47:03 |
| Message-ID: | 20090408164703.08ccdd83@dawn.webthatworks.it |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
postgresql suddenly died...
during recovery
2009-04-08 16:35:34 CEST FATAL: the database system is starting up
^^^ several
2009-04-08 16:35:34 CEST LOG: incomplete startup packet
2009-04-08 16:36:53 CEST FATAL: the database system is starting up
2009-04-08 16:36:53 CEST LOG: startup process (PID 3176) was
terminated by signal 11: Segmentation fault 2009-04-08 16:36:53 CEST
LOG: aborting startup due to startup process failure
It could be something wrong with the recovery process in an aborted
transaction that is causing the segfault...
How can I resurrect the server and load a backup?
It was serving more than one DB and I assume that only one is
causing problems. Can I skip just that one from recovery and start
from backup?
thanks
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jennifer Trey | 2009-04-08 14:50:39 | Re: Now I am back, next thing. Final PGS tuning. |
| Previous Message | Scott Mead | 2009-04-08 14:46:02 | Re: Now I am back, next thing. Final PGS tuning. |