| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: recovery after segmentation fault |
| Date: | 2009-04-08 14:59:54 |
| Message-ID: | 10910.1239202794@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> writes:
> 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
Hmm, what Postgres version is this? Can you get a stack trace from
the startup process crash?
The only simple way out of this is to delete the presumably-corrupt
WAL log by running pg_resetxlog. That will destroy the evidence
about what went wrong, though, so if you'd like to contribute to
preventing such problems in future you need to save a copy of everything
beforehand (eg, tar up all of $PGDATA). Also you might have a corrupt
database afterwards :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Radcon Entec | 2009-04-08 15:16:30 | Table has 22 million records, but backup doesn't see them |
| Previous Message | Jennifer Trey | 2009-04-08 14:50:39 | Re: Now I am back, next thing. Final PGS tuning. |