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 38A4DD1CAA2 for ; Fri, 30 Apr 2004 15:59:23 -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 17934-01 for ; Fri, 30 Apr 2004 15:59:03 -0300 (ADT) Received: from gpdnet.co.uk (gpdnet.plus.com [212.56.100.243]) by svr1.postgresql.org (Postfix) with ESMTP id 9BEB3D1E728 for ; Fri, 30 Apr 2004 15:59:01 -0300 (ADT) Received: from gary (unverified [192.168.1.2]) by gpdnet.co.uk (SurgeMail 1.8g3) with ESMTP id 424 for ; Fri, 30 Apr 2004 19:58:33 +0100 From: "Gary Doades" To: pgsql-performance@postgresql.org Date: Fri, 30 Apr 2004 19:59:38 +0100 MIME-Version: 1.0 Subject: Re: planner/optimizer question Message-ID: <4092B02A.15469.199EE3DE@localhost> In-reply-to: <409264C4.8060506@speedfc.com> References: <40920137.13806.16F37CC5@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Server: High Performance Mail Server - http://surgemail.com 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/528 X-Sequence-Number: 6828 On 30 Apr 2004 at 9:37, Kevin Barnard wrote: > > I was always under the impression that MSSQL used leaf and row level locking and therefore > was not a concurrent, in the same sense that postgres is, database. It would still allow for > concurrent connections and such but updates will get blocked/ delayed. I might be wrong. > Ultimately you may be right. I don't know enough about SQLServer internals to say either way. Anyway, most of our system is in selects for 70% of the time. I could try and set up a test for this when I get a bit more time. Unfortunately I suspect that this topic won't get taken much further. In order to test this it would mean modifying quite a bit of code. Whether putting additional info in the index header and not visiting the data row if all the required data is in the index would be beneficial would require quite a bit of work by someone who knows more than I do. I reckon that no-one has the time to do this at the moment. Regards, Gary.