Skip site navigation (1) Skip section navigation (2)

Re: could not read block 77 of relation 1663/16385/388818775

From: Alexandra Nitzschke <an(at)clickware(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Subject: Re: could not read block 77 of relation 1663/16385/388818775
Date: 2008-11-21 18:19:44
Message-ID: 4926FBC0.5070506@clickware.de (view raw or flat)
Thread:
Lists: pgsql-bugs
Yes, its a btree.


Tom Lane schrieb:
> Alexandra Nitzschke <an(at)clickware(dot)de> writes:
>> We have had a look at the /var/log files, no system crash, kernel panic or messages like this has happened.
> 
> What this smells like is a failed page split --- somewhere in the index
> there is a down-link pointing at page 77, but page 77 didn't actually
> get added to the file.
> 
> If there was no system crash or hardware misfeasance then that'd
> represent a Postgres bug, but it's difficult to do much about it
> unless you can come up with a reproducible sequence to trigger the bug.
> 
> (Also, since you didn't mention otherwise, I assume this is a btree
> index?)
> 
> 			regards, tom lane
> 
> 

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2008-11-21 18:26:02
Subject: Re: could not read block 77 of relation 1663/16385/388818775
Previous:From: Tom LaneDate: 2008-11-21 18:17:43
Subject: Re: executing SELECT xmlelement(name foo); causes "server closed the connection unexpectedly" Error

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group