From: Scott Marlowe <scott.marlowe@gmail.com>
To: Ansgar -59cobalt- Wiechers <lists@planetcobalt.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance on 8CPU's and 32GB of RAM
Date: Wed, 5 Sep 2007 19:12:04 -0500
Message-ID: <dcc563d10709051712q7f531ecew9fb31ed65dfc2dfa@mail.gmail.com> (raw)
In-Reply-To: <20070905231921.GA28600@mail.planetcobalt.net>
References: <fbkn5d$cfq$1@news.hub.org>
<dcc563d10709041615s305ae98bm92dee61ab199b7c4@mail.gmail.com>
<46DE66CF.9000903@theendofthetunnel.de>
<fbmhjt$d51$1@news.hub.org>
<dcc563d10709050845k135d3c2erbe5b44933e898aa@mail.gmail.com>
<90bce5730709051016j5291827dx525d6b8fe4960fbd@mail.gmail.com>
<dcc563d10709051236o60f852cdne392937704830200@mail.gmail.com>
<20070905210212.GA26941@mail.planetcobalt.net>
<dcc563d10709051459o21d41596t28bb730255a47925@mail.gmail.com>
<20070905231921.GA28600@mail.planetcobalt.net>
On 9/5/07, Ansgar -59cobalt- Wiechers <lists@planetcobalt.net> wrote:
> 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 if you look at my original reply, you'll see that I said WINDOWS /
NTFS. not just NTFS. i.e. it's a windowsism.
>
> > 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?
It doesn't. It's just not necessary to insult people to make a point.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: scott.marlowe@gmail.com, lists@planetcobalt.net
Subject: Re: Performance on 8CPU's and 32GB of RAM
In-Reply-To: <dcc563d10709051712q7f531ecew9fb31ed65dfc2dfa@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox