| Lists: | pgsql-bugspgsql-hackers |
|---|
| From: | anil maran <anilmrn(at)yahoo(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
| Subject: | 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 01:17:18 |
| Message-ID: | 20061122011718.49414.qmail@web55213.mail.re4.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs pgsql-hackers |
<AndrewSN> this needs to be posted on -hackers or -bugs, so that tom, oleg and teodor can take a look
Logs here
http://rafb.net/paste/results/NgHkIl17.html
Anil
____________________________________________________________________________________
Sponsored Link
Compare mortgage rates for today.
Get up to 5 free quotes. www2.nextag.com
| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | anil maran <anilmrn(at)yahoo(dot)com> |
| Cc: | 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 02:14:17 |
| Message-ID: | 20061122021417.GJ24662@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-bugs pgsql-hackers |
anil maran wrote:
>
> <AndrewSN> this needs to be posted on -hackers or -bugs, so that tom, oleg and teodor can take a look
> Logs here
> http://rafb.net/paste/results/NgHkIl17.html
Is this the same message you posted on -general? The error message was
PANIC: block 1100 unfound
I see several occurences of that message in gistxlog.c. Can you restart
the postmaster with "log_error_verbosity" set to "verbose" on
postgresql.conf, so that we have more details about it? Please post the
messages here on the list, not on a paste site.
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| 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 |
| 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