X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5D5F9D1E73F for ; Thu, 29 Apr 2004 20:18:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 29982-02 for ; Thu, 29 Apr 2004 20:17:53 -0300 (ADT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 5FE8AD1B43A for ; Thu, 29 Apr 2004 20:17:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i3TNHoSJ017899; Thu, 29 Apr 2004 19:17:50 -0400 (EDT) To: josh@agliodbs.com Cc: "Gary Doades" , pgsql-performance@postgresql.org Subject: Re: planner/optimizer question In-reply-to: <200404291354.33304.josh@agliodbs.com> References: <409153EF.24647.144E9BF7@localhost> <409172FA.1509.14C7E00E@localhost> <200404291354.33304.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Thu, 29 Apr 2004 13:54:33 -0700" Date: Thu, 29 Apr 2004 19:17:49 -0400 Message-ID: <17898.1083280669@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/513 X-Sequence-Number: 6813 Josh Berkus writes: > Certainly the fact that MSSQL is essentially a single-user database makes > things easier for them. Our recent testing (cf the "Xeon" thread) says that the interlocking we do to make the world safe for multiple backends has a fairly high cost (at least on some hardware) compared to the rest of the work in scenarios where you are doing zero-I/O scans of data already in memory. Especially so for index scans. I'm not sure this completely explains the differential that Gary is complaining about, but it could be part of it. Is it really true that MSSQL doesn't support concurrent operations? regards, tom lane