Dear Postgres Gurus
>
> Has there been any luck with this strange Postgres on OpenVZ edge case?
> We're also getting the 'could not read block' error.
>
> Warwick
>
On Monday, July 22, 2013, Warwick Chapman wrote:
>
>> =E1=CE=D4=CF=CE
>>
>> Did you manage to make any progress with OpenVZ and PostgreSQL on the
>> issue below in the last two years? We are running into the same problem
>> using OpenVZ VM's.
>>
>> -- Warwick Bruce Chapman | 081 270 1921 | http://wa.rwick.com
>>
>> From: =E1=CE=D4=CF=CE =F3=D4=C5=D0=C1=CE=C5=CE=CB=CF <zlobnynigga(at)yan=
dex(dot)ru>
>> To: Greg Smith <greg(at)2ndquadrant(dot)com>
>> Cc: pgsql-bugs(at)postgresql(dot)org
>> Subject: Re: could not read block XXXXX in file "base/YYYYY/ZZZZZZ":
>> read only 160 of 8192 bytes
>> Date: 2011-06-24 16:55:31
>> Message-ID: 1431308934531@web58.yandex.ru (view raw)
>>
>> 18.06.2011, 09:58, "Greg Smith" <greg(at)2ndQuadrant(dot)com>:
>> > I suspect you're running into some sort of OpenVZ shared memory handli=
ng
>> > bug. The way it handles this is one of the more complicated, and
>> > therefore likely to have odd failure cases, part of the design. There=
's
>> > notes at http://wiki.openvz.org/Postgresql_and_shared_memory about
>> > container-specific things to tune here, so maybe there's just a settin=
g
>> > to tweak you've missed so far. I'm guessing you already went through
>> > that though.
>> >
>> > A quick look around shows there are far more regularly reported bugs
>> > like this in OpenVZ than there are in PostgreSQL, and Ubuntu is not
>> > known for bug-free release practices either. You're probably chasing
>> > after the wrong thing trying to find a database problem here. Likely =
to
>> > end up in the same situation as the last one of these I remember:
>> >
>> > http://archives.postgresql.org/pgsql-general/2009-10/msg00125.php
>> > http://lists.debian.org/debian-kernel/2010/03/msg00401.html
>> >
>> > ...waiting for the OpenVZ problem that's the real cause to get fixed a=
nd
>> > make its way to your distribution.
>> >
>>
>> Finally I finded out that problem is in OpenVZ, you were right. I've
>> managed to set up one replica on "pure" Linux without OpenVZ. And it wor=
ks
>> for about a week already with 12Gb shared buffers.
>> I'm not sure what exactly is wrong with OpenVZ, but one thing that annoy=
s
>> me is that I have not the last stable OpenVZ kernel. I will try to compi=
le
>> the last one(unfortunately it requires new vzctl), and then run some tes=
ts
>> on it. And if it won't help - I'll go to OpenVZ community mailing lists =
and
>> brainfuck them =3D)
>> Thank you very much for your help, I appreciate it a lot. And sorry agai=
n
>> for my bad english.
>>
>>
>
> --
> -- Warwick Bruce Chapman | 081 270 1921 | http://wa.rwick.com
>
>