| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | anil maran <anilmrn(at)yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Error in postgresql after crash unable to restart this needs to be posted on -hackers or -bugs, so that tom, oleg and teodor can take a look |
| Date: | 2006-11-22 03:26:53 |
| Message-ID: | 21936.1164166013@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> anil maran wrote:
> PANIC: block 1100 unfound
> The next problem is determining which index is having the problem, and
> seeing if it has 1100 blocks or not. Maybe an extend operation was not
> logged, or something.
I'm thinking this might be the GIST variant of that
replay-after-truncation problem we fixed back in March. That is, the
xlog replay code isn't prepared for the possibility that the block it's
supposed to change no longer exists.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2006-11-22 04:46:08 | A bug or documentation error? |
| Previous Message | Alvaro Herrera | 2006-11-22 02:14:17 | Re: Error in postgresql after crash unable to restart this needs to be posted on -hackers or -bugs, so that tom, oleg and teodor can take a look |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-11-22 03:51:24 | Re: bad plan with custom data types |
| Previous Message | Alvaro Herrera | 2006-11-22 02:14:17 | Re: Error in postgresql after crash unable to restart this needs to be posted on -hackers or -bugs, so that tom, oleg and teodor can take a look |