Received: from crazypenguins.commandprompt.com (commandprompt.com [64.81.28.146]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f34M5W804988; Wed, 4 Apr 2001 18:05:32 -0400 (EDT) (envelope-from pma@commandprompt.com) Received: from commandprompt.com (gw [64.81.28.144]) by crazypenguins.commandprompt.com (8.9.3/8.9.3) with ESMTP id OAA28213; Wed, 4 Apr 2001 14:57:23 -0700 Message-ID: <3ACB9C4B.1071C2F1@commandprompt.com> Date: Wed, 04 Apr 2001 15:12:27 -0700 From: Phuong Ma Organization: Command Prompt, Inc. X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16-3 i586) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: performance inconsistency Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200104/205 X-Sequence-Number: 7284 Good day, We're running a week-old CVS snapshot of PostgreSQL 7.1, and I'm not sure if this performance inconsistency is specific to it, or if this is just something in PostgreSQL in general, but it seems kind of odd, and I could use some help here. ;) I have run two queries in a table full of invoices where the only difference between the queries is the where clause: SELECT COUNT(DISTINCT l."ORDER_NUM") AS line_orders, SUM(l."GROSS_PROFIT" + "REPLACEMENT_COST") AS grand_total, SUM(l."LIST_PRICE" * l."SHIPPED_QUANTITY") AS grand_total_alternative, SUM(l."GROSS_PROFIT") AS grand_total_profit FROM cu_invoice_li1_tbl l INNER JOIN cu_invoice_03_tbl h ON l."ORDER_NUM"=h."ORDER_NUM" WHERE substr("ORDER_NUM", 1, 1) != 'W'; # (Orders NOT prefixed with W.) OR... WHERE substr("ORDER_NUM", 1, 1) = 'I'; # (Orders prefixed with I.) The first query returns more rows than the second (because it includes orders prefixed with I, C, F, etc), whereas the second only returns orders prefixed with I. It seems that the logic of identifying a single character as *not* being a single value would be identical or at least similar in efficiency to the logic of a single character *being* being a single value. However, the first query runs in about 10-15 seconds, and the second query ran for over 40 minutes before I cancelled it. Now, I can easily use a series of "!=" statements to get it down so that it's only the 'I' orders (which runs even faster, at about 5-6 seconds!), but can anyone explain this to me? :) Are "!=" substring evaluations inherently faster by an obscene order of magnitude, or is something really wrong here? J.