| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | djlopes(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14440: Error starting postgres |
| Date: | 2016-11-30 00:46:27 |
| Message-ID: | 27860.1480466787@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
djlopes(at)gmail(dot)com writes:
> PostgreSQL version: 9.3.0
9.3.0? Really? There have been numerous and serious bugs fixed in the
9.3.x branch (I'm afraid it wasn't one of our most reliable releases).
I don't know offhand if any of them would explain this particular index
corruption, but you really need to be running something much newer.
9.3.15 is the current release in that branch.
> 2016-11-29 23:27:17 WET FATAL: btree level 1 not found in index "77469"
> 2016-11-29 23:27:17 WET LOG: startup process (PID 4971) exited with exit
> code 1
> 2016-11-29 23:27:17 WET LOG: aborting startup due to startup process
> failure
Looks like severe corruption of an index. I do not think there's any
automated way to recover from this. If you don't want to revert to your
last backups (hopefully you have some) it's going to take manual forensic
analysis to see what can be extracted. There are various support
companies that specialize in Postgres data recovery ... it's unlikely
anyone will want to do it for free.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mark.pether | 2016-11-30 01:17:10 | BUG #14441: trim function bug (hit a keyword somewhere internally) |
| Previous Message | Tom Lane | 2016-11-30 00:01:16 | Re: parallel sequential scan returns extraneous rows |