Re: Extend win32 error codes to errno mapping in win32error.c

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-09-28T05:56:05Z
Lists: pgsql-hackers
On Wed, Sep 28, 2022 at 11:14:53AM +0530, Bharath Rupireddy wrote:
> IMO, we can add mapping for just ERROR_INVALID_NAME which is an
> obvious error code and easy to hit, leaving others. There are actually
> many win32 error codes that may get hit in our code base and actually
> mapping everything isn't possible.

Yes.  I am fine to do just that as you have managed to hit it during
development.  The others may have more opinions to offer.
--
Michael

Commits

  1. Map ERROR_INVALID_NAME to ENOENT in mapping table of win32error.c