On Mon, Dec 16, 2024 at 12:52 PM Andres Freund <and...@anarazel.de> wrote:
> I don't see what we gain by requiring guesswork (what does allocating vs
> zeroing mean, zeroing also allocates disk space after all) to interpret the
> main error message. My experience is that it's often harder to get the DETAIL
> than the actual error message (grepping becomes harder due to separate line,
> terse verbosity is commonly used).
I feel like the normal way that we do this is basically:
could not {name of system call} file "\%s\": %m
e.g.
could not read file \"%s\": %m
I don't know why we should do anything else in this type of case.
--
Robert Haas
EDB: http://www.enterprisedb.com
