Skip site navigation (1) Skip section navigation (2)

Re: pgwin32_open returning EINVAL

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgwin32_open returning EINVAL
Date: 2007-11-29 20:59:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Magnus Hagander <magnus(at)hagander(dot)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

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-11-29 21:11:55
Subject: Re: [GENERAL] Empty arrays with ARRAY[]
Previous:From: Magnus HaganderDate: 2007-11-29 20:45:45
Subject: Re: pgwin32_open returning EINVAL

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group