Postgres Pro
Downloads
Home   >   mailing lists

BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes - Mailing list pgsql-bugs

From mayank.mittal.1982@hotmail.com
Subject BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes
Date
Msg-id E1TEjPD-0002Yq-7L@wrigleys.postgresql.org
Whole thread Raw
Responses Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: BUG #7562: could not read block 0 in file "base/16385/16585": read only 0 of 8192 bytes  (Mayank Mittal <mayank.mittal.1982@outlook.com>)
List pgsql-bugs
Tree view 
The following bug has been logged on the website:

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:        =


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.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #7559: syslogger doesn't close stdout and stderr
Next
From: Tom Lane
Date:
Subject: Re: BUG #7559: syslogger doesn't close stdout and stderr