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 |
Thread: | |
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 | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-11-22 03:26:53 | 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 |
Previous Message | anil maran | 2006-11-22 01:17:18 | 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:26:53 | 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 |
Previous Message | Greg Mitchell | 2006-11-22 01:17:26 | bad plan with custom data types |