Re: could not read block XXXXX in file "base/YYYYY/ZZZZZZ": read only 160 of 8192 bytes - Mailing list pgsql-bugs

From Merlin Moncure
Subject Re: could not read block XXXXX in file "base/YYYYY/ZZZZZZ": read only 160 of 8192 bytes
Date
Msg-id BANLkTim0hL_VkkU7=ozYzRP5+Ruw-BcDuQ@mail.gmail.com
Whole thread Raw
In response to Re: could not read block XXXXX in file "base/YYYYY/ZZZZZZ": read only 160 of 8192 bytes  (Антон Степаненко <zlobnynigga@yandex.ru>)
Responses Re: could not read block XXXXX in file "base/YYYYY/ZZZZZZ": read only 160 of 8192 bytes
List pgsql-bugs
2011/6/17 =E1=CE=D4=CF=CE =F3=D4=C5=D0=C1=CE=C5=CE=CB=CF <zlobnynigga@yande=
x.ru>:
>
>
> 17.06.2011, 20:19, "Merlin Moncure" <mmoncure@gmail.com>:
>> On Fri, Jun 17, 2011 at 10:56 AM, Kevin Grittner
>> <Kevin.Grittner@wicourts.gov>; wrote:
>>
>>>> =9AI still do not believe that this is hardware problem.
>>> =9AHow would an application cause a bus error?
>>
>> unaligned memory access on risc maybe? =9Awhat's this running on?
>>
>> merlin
>
> *****:~$ cat /proc/cpuinfo
> processor =9A =9A =9A : 0
> ....
> processor =9A =9A =9A : 23
> vendor_id =9A =9A =9A : GenuineIntel
> cpu family =9A =9A =9A: 6
> model =9A =9A =9A =9A =9A : 44
> model name =9A =9A =9A: Intel(R) Xeon(R) CPU =9A =9A =9A =9A =9A E5645 =
=9A@ 2.40GHz

hm, I'm wondering if this
(http://us.generation-nt.com/bug-626451-linux-image-mremap-returns-useless-=
pages-moving-anonymous-shared-mmap-access-causes-sigbus-help-203302832.html)
has anything to do with your problem.

merlin

pgsql-bugs by date:

Previous
From: Антон Степаненко
Date:
Subject: Re: could not read block XXXXX in file "base/YYYYY/ZZZZZZ": read only 160 of 8192 bytes
Next
From: Tom Lane
Date:
Subject: Re: Ident authentication fails due to bind error on server (8.4.8)