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 2A5E1D1E7C0 for ; Thu, 29 Apr 2004 20:01:00 -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 17063-10 for ; Thu, 29 Apr 2004 20:00:42 -0300 (ADT) Received: from gpdnet.co.uk (gpdnet.plus.com [212.56.100.243]) by svr1.postgresql.org (Postfix) with ESMTP id 351EAD1E321 for ; Thu, 29 Apr 2004 20:00:38 -0300 (ADT) Received: from gary (unverified [192.168.1.2]) by gpdnet.co.uk (SurgeMail 1.8g3) with ESMTP id 268 for ; Fri, 30 Apr 2004 00:00:08 +0100 From: "Gary Doades" To: pgsql-performance@postgresql.org Date: Fri, 30 Apr 2004 00:01:10 +0100 MIME-Version: 1.0 Subject: Re: planner/optimizer question Message-ID: <40919746.25550.1555A9CC@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/510 X-Sequence-Number: 6810 > > Having picked out an index scan as being the highest time user I > concentrated on that in this case and compared the same index scan on > MSSQL. At least MSSQL reported it as an index scan on the same index > for the same number of rows. > I should have also pointed out that MSSQL reported that same index scan as taking 65% of the overall query time. It was just "faster". The overall query took 103ms in MSSQL. Gary.