Remove rangechecks on errno; just call strerror unconditionally. This

Tom Lane <tgl@sss.pgh.pa.us>

Commit: e9c936ff38da738d1fd68525eee9c7c1f0c558dc
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2001-01-22T23:28:52Z
Releases: 7.1.1
Remove rangechecks on errno; just call strerror unconditionally.  This
eliminates a raft of portability issues, including whether sys_nerr
exists, whether the platform has any valid negative errnos, etc.  The
downside is minimal: errno shouldn't ever contain an invalid value anyway,
and if it does, reasonably modern versions of strerror will not choke.
This rangecheck idea seemed good at the time, but it's clearly a net loss,
and I apologize to all concerned for having ever put it in.

Files

PathChange+/−
config/c-library.m4 modified +1 −17
configure modified +47 −81
configure.in modified +0 −2
src/backend/utils/error/elog.c modified +2 −13
src/backend/utils/error/exc.c modified +2 −13
src/include/config.h.in modified +1 −4