Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id B3AB2476767 for ; Thu, 2 Jan 2003 15:34:32 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 232D7476DD1 for ; Thu, 2 Jan 2003 15:24:21 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h02KOK0U003560; Thu, 2 Jan 2003 15:24:20 -0500 (EST) To: Hilmar Lapp Cc: pgsql-performance@postgresql.org Subject: Re: join over 12 tables takes 3 secs to plan In-reply-to: <43D30901-1E8A-11D7-9244-000393B4BFF6@gmx.net> References: <43D30901-1E8A-11D7-9244-000393B4BFF6@gmx.net> Comments: In-reply-to Hilmar Lapp message dated "Thu, 02 Jan 2003 11:42:02 -0800" Date: Thu, 02 Jan 2003 15:24:20 -0500 Message-ID: <3559.1041539060@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/7 X-Sequence-Number: 654 Hilmar Lapp writes: > I have a query generated by an application (not mine, but there's > nothing I can find that looks bad about the query itself) that takes an > excessive amount of time to return even though there are almost no rows > in the schema yet. Read http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/explicit-joins.html regards, tom lane