Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 6F3679FB3BC for ; Fri, 7 Sep 2007 13:22:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 45327-02 for ; Fri, 7 Sep 2007 13:21:55 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by postgresql.org (Postfix) with ESMTP id A4E0A9FB42E for ; Fri, 7 Sep 2007 13:16:40 -0300 (ADT) Received: by rv-out-0910.google.com with SMTP id l15so452913rvb for ; Fri, 07 Sep 2007 09:16:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=4CXTiAiJk9zGurGqqrQpF1h5PF53DS/H6SBsJykZYR0=; b=hZGItOv0ouuiSL5UkIXG05RMpbone/t9Q8+n/omDAQNzOMGHeG2wWUYXaYX2mbKDremjHhD248BuJAMLg202JT+xvOr7yt0A0DRuBxGdBiU8eizECPM3fm+/OdZMrVDefP3f30ktuM3mhenFlln0XP4WjOTtgh5sWBlGmv4QDkg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dPmJcCX044wgv6HPIwPkh63OR87LrgomRA/rZyret840v/Fpx1WfQV4DwKhSzKAQJSA//bs4xuHGnDZf1pZVMbbyOfYbn8GFhTweIvWmHc4HbE2dTPckyx1Ml3glqaRDqRHoJ27xSigs5PnrwiGtJqnGTWMLw7icWkCX8rNS+Aw= Received: by 10.141.90.17 with SMTP id s17mr789803rvl.1189181798215; Fri, 07 Sep 2007 09:16:38 -0700 (PDT) Received: by 10.141.159.11 with HTTP; Fri, 7 Sep 2007 09:16:38 -0700 (PDT) Message-ID: Date: Fri, 7 Sep 2007 11:16:38 -0500 From: "Scott Marlowe" To: "Florian Weimer" Subject: Re: Performance on 8CPU's and 32GB of RAM Cc: "Trevor Talbot" , pgsql-performance@postgresql.org In-Reply-To: <82ir6mnb3s.fsf@mid.bfk.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070904230639.GA23731@alvh.no-ip.org> <46DE66CF.9000903@theendofthetunnel.de> <90bce5730709051016j5291827dx525d6b8fe4960fbd@mail.gmail.com> <82ir6mnb3s.fsf@mid.bfk.de> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/128 X-Sequence-Number: 26673 On 9/7/07, Florian Weimer 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.