Re: pgwin32_open returning EINVAL
От | Magnus Hagander |
---|---|
Тема | Re: pgwin32_open returning EINVAL |
Дата | |
Msg-id | 20071219141121.GP11226@svr2.hagander.net обсуждение исходный текст |
Ответ на | Re: pgwin32_open returning EINVAL (Gregory Stark <stark@enterprisedb.com>) |
Список | pgsql-hackers |
On Wed, Dec 19, 2007 at 01:05:00PM +0000, Gregory Stark wrote: > "Magnus Hagander" <magnus@hagander.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. Then you're wrong. You can open files in shared mode no problem - it's how we have multiple backensd opening the same file. You do have to remember to specify the flag when you open the file - something backup software for example has always done, unless it's really crappy design. Most proper backup software will use VSS these days, which makes the whole point moot. And antivirus is supposed to be entirely transparent, so it's definitely a bug when it happens. But we've seen a lot of buggy antivirus. //Magnus
В списке pgsql-hackers по дате отправления: