Re: Checkpoint not retrying failed fsync?

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
Subject: Re: Checkpoint not retrying failed fsync?
Date: 2018-07-13 04:44:19
Message-ID: CAEepm=0v3UX3vOgyK4zL_bJK=PTDf5mWLOSU+3zJ99T+EOmwWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 12, 2018 at 3:31 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> I was about to mark this patch "rejected" and forget about it, since
> Craig's patch makes it redundant. But then I noticed that Craig's
> patch doesn't actually remove the retry behaviour completely: it
> promotes only EIO and ENOSPC to PANIC.

Rejected, since this will have to be dealt with one way or another in
that other thread.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-07-13 04:50:27 Re: Cannot dump foreign key constraints on partitioned table
Previous Message Michael Paquier 2018-07-13 04:40:14 Re: [PATCH] Timestamp for a XLOG_BACKUP_END WAL-record