From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "Ansgar -59cobalt- Wiechers" <lists(at)planetcobalt(dot)net> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Performance on 8CPU's and 32GB of RAM |
Date: | 2007-09-05 21:59:17 |
Message-ID: | dcc563d10709051459o21d41596t28bb730255a47925@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 9/5/07, Ansgar -59cobalt- Wiechers <lists(at)planetcobalt(dot)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.
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Tauno Williams | 2007-09-05 22:15:58 | Re: Performance on 8CPU's and 32GB of RAM |
Previous Message | Trevor Talbot | 2007-09-05 21:08:41 | Re: Performance on 8CPU's and 32GB of RAM |