Re: pgwin32_open returning EINVAL

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Magnus Hagander" <magnus(at)hagander(dot)net>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "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-12-19 13:05:00
Message-ID: 87fxxyn8cj.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Magnus Hagander" <magnus(at)hagander(dot)net> writes:

> If your software is locking a file for that long, that software is more
> than just broken, it's horribly broken. Having a workaround against
> something that might happen once or twice because of a bug in the other
> software is one thing, but if it's actually *designed* to do that you
> really need to get that software removed from your machine.

I was under the impression though that this was just how open worked on
windows. Only one process can have a file open at the same time.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2007-12-19 13:09:39 Re: Testing mail list
Previous Message Magnus Hagander 2007-12-19 12:52:32 Re: pgwin32_open returning EINVAL