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 - Mailing list pgsql-hackers

From Alvaro Herrera
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
Msg-id 20061122021417.GJ24662@alvh.no-ip.org
Whole thread Raw
In response to 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  (anil maran <anilmrn@yahoo.com>)
Responses 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  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] backup + restore fails
Next
From: Tom Lane
Date:
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