Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id ED4D99FB22B for ; Fri, 29 Sep 2006 01:31:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 04918-01 for ; Fri, 29 Sep 2006 04:30:28 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id A671A9FA5DC for ; Fri, 29 Sep 2006 01:30:27 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id A0E8E30E2D; Fri, 29 Sep 2006 06:30:26 +0200 (MET DST) From: "Carlo Stonebanks" X-Newsgroups: pgsql.performance Subject: Re: Performace Optimization for Dummies Date: Fri, 29 Sep 2006 00:30:23 -0400 Organization: Hub.Org Networking Services Lines: 13 Message-ID: References: <5EE4B6D1-8ECE-4033-A912-DFD9146A5A93@blighty.com> <6B702C4D-C102-44E3-841C-BF176EAF1CAB@blighty.com> <20060928235243.GH34238@nasby.net> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-RFC2646: Format=Flowed; Original To: pgsql-performance@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/414 X-Sequence-Number: 21100 > Something else to consider... databases love doing bulk operations. It > might be useful to load prospective data into a temporary table, and > then do as many operations as you can locally (ie: within the database) > on that table, hopefully eleminating as many candidate rows as possible > along the way. I wish this would work... it was definitely something I considered early on in the project. Even thinking of explaining why it won't work is giving me a headache... But I sure wish it would.