Re: Fix some error handling for read() and errno
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Robbie Harwood <rharwood@redhat.com>,
Michael Paquier <michael@paquier.xyz>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, hlinnaka <hlinnaka@iki.fi>
Date: 2018-06-14T13:50:33Z
Lists: pgsql-hackers
On Mon, Jun 11, 2018 at 6:11 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > I would go as far as suggesting to remove qualifiers that indicate what > the file is for (such as "relation mapping file"); relying on the path > as indicator of what's going wrong should be sufficient, since it's an > error that affects internals anyway, not anything that users can do much > about. Keep variations to a minimum, to ease translator's work; > sometimes it's hard enough to come up with good translations for things > like "relation mapping file" in the first place, and they don't help the > end user. +1. I think those things are often hard to phrase even in English. It makes the messages long, awkward, and almost invariably the style differs from one message to the next depending on the author and how easy it is to describe the type of file involved. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Rework error messages around file handling
- 811b6e36a9e2 12.0 landed