pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: TAKATSUKA Haruka <harukat@sraoss.co.jp>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Michael Paquier <michael@paquier.xyz>
Subject: Re: fix "Success" error messages
Date: Thu, 21 Nov 2019 10:40:36 +0100
Message-ID: <5457fd8b-67e1-d399-b4d6-075776fed71a@2ndquadrant.com> (raw)
In-Reply-To: <20191121104257.a3010b3ec22f83e498147f74@sraoss.co.jp>
References: <5de61b6b-8be9-7771-0048-860328efe027@2ndquadrant.com>
	<20190618161319.GA5285@f01898859afd.ant.amazon.com>
	<20190619025155.GD17450@paquier.xyz>
	<36d38542-63e9-b73c-09fe-bd5e32e06066@2ndquadrant.com>
	<20190827062726.GF7422@paquier.xyz>
	<9cc51628-163c-2cc1-c9a7-cd03d1ed89ef@2ndquadrant.com>
	<20190927155239.GB31412@momjian.us>
	<20191121104257.a3010b3ec22f83e498147f74@sraoss.co.jp>

On 2019-11-21 02:42, TAKATSUKA Haruka wrote:
>   FATAL: could not access status of transaction ..
>   DETAIL: Could not read from file (pg_clog/.... or pg_xact/....) ...: Success.
> 
> This error has caused the server to fail to start with recovery.
> I got a report that it happend repeatedly at the newly generated
> standby cluster. I gave them advice to comfirm the low level server
> environment.
> 
> However, in addition to improving the message, should we retry to read
> the rest of the data in the case reading too few bytes?
> What about a limited number of retries instead of a complete loop?

If we thought that would help, there are probably hundreds or more other 
places where we read files that would need to be fixed up in the same 
way.  That doesn't seem reasonable.

Also, it is my understanding that short reads can in practice only 
happen if the underlying storage is having a serious problem, so 
retrying wouldn't actually help much.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (10+ messages)  latest in thread

Message-ID: <5457fd8b-67e1-d399-b4d6-075776fed71a@2ndquadrant.com>
Permalink:  ../5457fd8b-67e1-d399-b4d6-075776fed71a@2ndquadrant.com/
Also on:    postgresql.org/message-id/5457fd8b-67e1-d399-b4d6-075776fed71a@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, harukat@sraoss.co.jp, michael@paquier.xyz
  Subject: Re: fix "Success" error messages
  In-Reply-To: <5457fd8b-67e1-d399-b4d6-075776fed71a@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox