pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Ansgar -59cobalt- Wiechers <lists@planetcobalt.net>
To: pgsql-performance@postgresql.org
Subject: Re: Performance on 8CPU's and 32GB of RAM
Date: Thu, 6 Sep 2007 01:19:21 +0200
Message-ID: <20070905231921.GA28600@mail.planetcobalt.net> (raw)
In-Reply-To: <dcc563d10709051459o21d41596t28bb730255a47925@mail.gmail.com>
References: <fbkn5d$cfq$1@news.hub.org>
	<20070904230639.GA23731@alvh.no-ip.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>

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



view thread (35+ messages)  latest in thread

Message-ID: <20070905231921.GA28600@mail.planetcobalt.net>
Permalink:  ../20070905231921.GA28600@mail.planetcobalt.net/
Also on:    postgresql.org/message-id/20070905231921.GA28600@mail.planetcobalt.net

 · 

reply
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: lists@planetcobalt.net
  Subject: Re: Performance on 8CPU's and 32GB of RAM
  In-Reply-To: <20070905231921.GA28600@mail.planetcobalt.net>

* 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