Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 0D7762E2D7D for ; Fri, 16 Nov 2007 16:54:01 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 25591-03 for ; Fri, 16 Nov 2007 16:53:40 -0400 (AST) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by postgresql.org (Postfix) with ESMTP id 35A3F2E2D3E for ; Fri, 16 Nov 2007 16:53:53 -0400 (AST) Received: by nz-out-0506.google.com with SMTP id l8so963459nzf for ; Fri, 16 Nov 2007 12:53:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=BOJryqKIwg8732TPB/5waLqaq85yN95B7ApYZFdajqg=; b=dy0HYCEFEyQvQpb0IvgCJT7pGK7d6xmYyFwZDD9bJ6E139hFsau+HfHF8d6Va/oFeD7+x/JgYq59g5BKQjdsDxCLyZLaRX7iFolN4pnO9gjAsUVmM2ZTzZ4RXRZTDUrPpkxXR+kl08XmnpeXNd8ufd4UumiKdKh+BsMiQzap07Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=P5FGyDvumYEe4FRbIruTyC960stbHZobhmqtAjjasrRDgkGO85At0QEW/amS64EWBWIVcUNR7a+pAQe3we7iBrCKefpnudEyfrTib0MY+fjJqfP1ASqTbbGAKHxnYGSl7+htzPR8kqfWFMKBrViVn/5fBjIr2eP7uC5vH6RKbrc= Received: by 10.142.242.8 with SMTP id p8mr758714wfh.1195246431481; Fri, 16 Nov 2007 12:53:51 -0800 (PST) Received: by 10.143.8.5 with HTTP; Fri, 16 Nov 2007 12:53:51 -0800 (PST) Message-ID: <36e682920711161253l4376c96ap95fb494c7e24874f@mail.gmail.com> Date: Fri, 16 Nov 2007 15:53:51 -0500 From: "Jonah H. Harris" To: "Josh Trutwin" Subject: Re: PostgreSQL vs MySQL, and FreeBSD Cc: pgsql-performance@postgresql.org In-Reply-To: <20071116143650.03e994ad@prokofiev.trutwins.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47344D43.5090506@geri.cc.fer.hr> <47347F9F.1070309@laliluna.de> <1195206185.29253.56.camel@neuromancer.home.net> <01c601c82869$3ffb2580$8e00a8c0@tridecap.com> <36e682920711160806k359a8825ia0d962d7ac6f6d7b@mail.gmail.com> <20071116143650.03e994ad@prokofiev.trutwins.homeip.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/251 X-Sequence-Number: 27666 On Nov 16, 2007 3:36 PM, Josh Trutwin wrote: > > Agreed. IMHO, there's nothing wrong with nested-loop join as long > > as it's being used properly. > > Can you explain further please? (I'm not disagreeing with you, just > want to know when nested loops are not used properly - does the > planner make mistakes that you have to watch out for?) As long as statistics are updated properly, it's generally not an issue. You just don't want the system using a nested-loop join incorrectly (like when table sizes are equal, the outer table is larger than the inner table, or the inner table itself is overly large). -- Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324 EnterpriseDB Corporation | fax: 732.331.1301 499 Thornall Street, 2nd Floor | jonah.harris@enterprisedb.com Edison, NJ 08837 | http://www.enterprisedb.com/