| From: | m(dot)sakrejda(at)gmail(dot)com |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #7752: FATAL btree error on PITR |
| Date: | 2012-12-12 01:55:13 |
| Message-ID: | E1TibXV-0006fM-H2@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 7752
Logged by: Maciek Sakrejda
Email address: m(dot)sakrejda(at)gmail(dot)com
PostgreSQL version: 9.1.6
Operating system: Ubuntu 10.04 LTS 64-bit
Description:
Ran into the following error in trying to perform a PITR:
FATAL: btree level 66135134 not found in index "436254"
This happened when the PITR was almost complete (judging by on-disk database
size). I guess this may be related to one of the index corruption issues
fixed in 9.1.7, but if that's the case, would it perhaps make sense to
complete the PITR without the corrupt index(es) and deal with the index
issue separately? Clearly, just a warning is dangerously likely to be
skipped, but maybe a mechanism like backup_label, that prevents normal
startup before the issue is resolved?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-12-12 03:11:26 | Re: init_htab causes SIGFPE (or worse) due to miscalculation for large nbuckets |
| Previous Message | ktuszynska | 2012-12-11 23:08:53 | BUG #7751: libintl.h missing in the include folder |