On 2007-09-05 Scott Marlowe wrote:
> On 9/5/07, Ansgar -59cobalt- Wiechers <lists@planetcobalt.net> wrote:
>> On 2007-09-05 Scott Marlowe wrote:
>>> And there's the issue that with windows / NTFS that when one process
>>> opens a file for read, it locks it for all other users. This means
>>> that things like virus scanners can cause odd, unpredictable
>>> failures of your database.
>>
>> Uh... what? Locking isn't done by the filesystem but by applications
>> (which certainly can decide to not lock a file when opening it). And
>> no one in his right mind would ever have a virus scanner access the
>> files of a running database, regardless of operating system or
>> filesystem.
>
> Exactly, the default is to lock the file. The application has to
> explicitly NOT lock it. It's the opposite of linux.
Yes. So? It's still up to the application, and it still has nothing at
all to do with the filesystem.
> And be careful, you're insulting a LOT of people who have come on this
> list with the exact problem of having their anti-virus scramble the
> brain of their postgresql installation. It's a far more common
> problem than it should be.
How does that make it any less stup^Wintellectually challenged?
Regards
Ansgar Wiechers
--
"The Mac OS X kernel should never panic because, when it does, it
seriously inconveniences the user."
--http://developer.apple.com/technotes/tn2004/tn2118.html
