Here is a snapshot of installed postgresql packages: mayank@server:~$ dpkg -l | grep postgres
ii postgresql-9.1 9.1.5-1~bpo60+1 object-relational SQL database, version 9.1 server ii postgresql-client-9.1 9.1.5-1~bpo60+1 front-end programs for PostgreSQL 9.1 ii postgresql-client-common 130~bpo60+1 manager for multiple PostgreSQL client versions ii postgresql-common 130~bpo60+1 PostgreSQL database-cluster manager ii postgresql-contrib 9.1+130~bpo60+2 additional facilities for PostgreSQL (supported version) ii postgresql-contrib-9.1 9.1.5-1~bpo60+1 additional facilities for PostgreSQL Regards, Mayank Mittal > Date: Thu, 20 Sep 2012 16:15:11 +0000 > Subject: [BUGS] BUG #7562: could not read block 0 in file "base/16385/16585": > read only 0 of 8192 bytes > To: pgsql-bugs@postgresql.org > From: mayank.mittal.1...@hotmail.com > > The following bug has been logged on the website: > > Bug reference: 7562 > Logged by: Mayank Mittal > Email address: mayank.mittal.1...@hotmail.com > PostgreSQL version: 9.1.5 > Operating system: Debian Linux 6.0 > Description: > > 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. > 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 Corosync > and Heartbeat. > My application is requirement needs heavy database updates. Upon fail-over > I've noticed that database indexes got corrupted. > 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, but we are facing the same. > > > > > > -- > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs
