Re: Fix some error handling for read() and errno
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Magnus Hagander <magnus@hagander.net>, Robbie Harwood <rharwood@redhat.com>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, hlinnaka <hlinnaka@iki.fi>
Date: 2018-06-22T23:48:03Z
Lists: pgsql-hackers
On Fri, Jun 22, 2018 at 09:51:30AM -0400, Alvaro Herrera wrote: > On 2018-Jun-22, Robert Haas wrote: >> I think this should be split into two patches. Fixing failure to save >> and restore errno is a different issue from cleaning up short write >> messages. I agree that the former should be back-patched and the >> latter not. > > Hmm, yeah, good thought, +1. That's exactly why I have started this thread so as both problems are addressed separately: https://www.postgresql.org/message-id/20180622061535.GD5215@paquier.xyz And back-patching the errno patch while only bothering about messages on HEAD matches also what I got in mind. I'll come back to this thread once the errno issues are all addressed. -- Michael
Commits
-
Rework error messages around file handling
- 811b6e36a9e2 12.0 landed