Re: pgwin32_open returning EINVAL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgwin32_open returning EINVAL
Date
Msg-id 18671.1196369984@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgwin32_open returning EINVAL  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pgwin32_open returning EINVAL  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> Tom Lane wrote:
>> I'm still not convinced what you think the problematic situation is.

> I believe Alvaros point is that several different GetLastError codes map
> to the same errno code, making it impossible to see the difference
> between those errors.

(1) If we need to know the difference, then we shouldn't be mapping them
to the same thing.

(2) Do we have any live cases where we must know this?  Much less enough
cases to justify a global increase in the log chattiness?  It's not like
we cannot get the information if we really need it.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pgwin32_open returning EINVAL
Next
From: Tom Lane
Date:
Subject: Re: [GENERAL] Empty arrays with ARRAY[]