Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes

Here is a snapshot of installed postgresql packages:
mayank@server:~$ dpkg -l | grep postgres=0A=
=0A=
ii =0A=
postgresql-9.1                     =0A=
9.1.5-1~bpo60+1             =0A=
object-relational SQL database=2C version 9.1 server=0A=
=0A=
ii =0A=
postgresql-client-9.1              =0A=
9.1.5-1~bpo60+1             =0A=
front-end programs for PostgreSQL 9.1=0A=
=0A=
ii =0A=
postgresql-client-common           =0A=
130~bpo60+1                 =0A=
manager for multiple PostgreSQL client versions=0A=
=0A=
ii  postgresql-common                  =0A=
130~bpo60+1                 =0A=
PostgreSQL database-cluster manager=0A=
=0A=
ii =0A=
postgresql-contrib                 =0A=
9.1+130~bpo60+2             =0A=
additional facilities for PostgreSQL (supported=0A=
version)=0A=
=0A=
ii =0A=
postgresql-contrib-9.1             =0A=
9.1.5-1~bpo60+1             =0A=
additional facilities for PostgreSQL
Regards=2C
Mayank Mittal


> Date: Thu=2C 20 Sep 2012 16:15:11 +0000
> Subject: [BUGS] BUG #7562: could not read block 0 in file "base/16385/165=
85": read    only 0 of 8192 bytes
> To: pgsql-bugs@postgresql.org
> From: mayank.mittal.1982@hotmail.com
>=20
> The following bug has been logged on the website:
>=20
> Bug reference:      7562
> Logged by:          Mayank Mittal
> Email address:      mayank.mittal.1982@hotmail.com
> PostgreSQL version: 9.1.5
> Operating system:   Debian Linux 6.0
> Description:       =20
>=20
> We are using 2 node set-up of PostgreSQL 9.1.5 in which one is master and
> other is slave which is in sync of master with streaming replication.=20
> The design is in such a way that in case of master node failure the slave
> node has to take master role. I'm controlling this behaviour using Corosy=
nc
> and Heartbeat.
> My application is requirement needs heavy database updates. Upon fail-ove=
r
> I've noticed that database indexes got corrupted.=20
> I'm not sure why this is happening. I was referring release notes of 9.1.=
3
> and found similar issue is already fixed in it=2C but we are facing the s=
ame.
>=20
>=20
>=20
>=20
>=20
> --=20
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
                           =