pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Florian Weimer <fweimer@bfk.de>
Cc: Trevor Talbot <quension@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Performance on 8CPU's and 32GB of RAM
Date: Fri, 7 Sep 2007 11:16:38 -0500
Message-ID: <dcc563d10709070916n6a0a0a1cra17a244648b67be7@mail.gmail.com> (raw)
In-Reply-To: <82ir6mnb3s.fsf@mid.bfk.de>
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>
	<82ir6mnb3s.fsf@mid.bfk.de>

On 9/7/07, Florian Weimer <fweimer@bfk.de> wrote:
> * Scott Marlowe:
>
> > 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.
>
> I think most of them open the file in shared/backup mode.  The only
> lock that is created by that guards deletion and renaming.  It can
> still lead to obscure failures, but it's not a wholly-eclusive lock.

Well, there've been a lot of issues with anti-virus and postgresql not
getting along.  I wonder if pgsql takes out a stronger lock, and when
it can't get it then the failure happens.  Not familiar enough with
windows to do more than speculate.



view thread (35+ messages)  latest in thread

Message-ID: <dcc563d10709070916n6a0a0a1cra17a244648b67be7@mail.gmail.com>
Permalink:  ../dcc563d10709070916n6a0a0a1cra17a244648b67be7@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d10709070916n6a0a0a1cra17a244648b67be7@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, fweimer@bfk.de, quension@gmail.com
  Subject: Re: Performance on 8CPU's and 32GB of RAM
  In-Reply-To: <dcc563d10709070916n6a0a0a1cra17a244648b67be7@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> <82ir6mnb3s.fsf@mid.bfk.de> <dcc563d10709070916n6a0a0a1cra17a244648b67be7@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