BUG #14118: ERROR: could not read block 0 in file causes the application goes down - Mailing list pgsql-bugs

From yuqiang.liao@polycom.com
Subject BUG #14118: ERROR: could not read block 0 in file causes the application goes down
Date
Msg-id 20160428084122.19112.65187@wrigleys.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      14118
Logged by:          Yuqiang
Email address:      yuqiang.liao@polycom.com
PostgreSQL version: 9.3.6
Operating system:   CentOS 6.6
Description:

Hi,

Our system encountered the error twice with the same exception as below --

<179>1 2015-10-31T19:52:19.989+01:00 E11VRPRM01.pharma.xxxxxx.com RPRM 15898
Jserver - ERROR|||main|com.xxxxxx.rm.db.AbstractDomainDao| Unable to add
instance of SystemAlert to database.
<179>1 2015-10-31T19:52:19.989+01:00 E11VRPRM01.pharma.xxxxxx.com RPRM 15898
Jserver - org.springframework.jdbc.UncategorizedSQLException:
PreparedStatementCallback; uncategorized SQLException for SQL [INSERT INTO
SystemAlerts (alerttype, note, createdate, updatedate, updateby) values
(?,?,?,?,?)]; SQL state [XX001]; error code [0]; ERROR: could not read block
0 in file "pg_tblspc/16403/PG_9.3_201306121/16405/20189": read only 0 of
8192 bytes;

I see there is a bug tracking the similar issue but I'd like to know the
clear workaround instruction.

http://www.postgresql.org/message-id/87tx0dc80x.fsf@news-spur.riddles.org.uk

Thanks!

pgsql-bugs by date:

Previous
From: Кирковский Александр
Date:
Subject: Bug report
Next
From: Andres Freund
Date:
Subject: Re: streaming replication master can fail to shut down