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 66E0FD1EB5F for ; Fri, 2 Apr 2004 15:46:25 +0000 (GMT) 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 69256-01 for ; Fri, 2 Apr 2004 11:46:27 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 99D67D1EB47 for ; Fri, 2 Apr 2004 11:46:22 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i32FkRkc027944; Fri, 2 Apr 2004 10:46:27 -0500 (EST) To: Clive Page Cc: pgsql-performance@postgresql.org Subject: Re: Spatial join insists on sequential scan of larger table In-reply-to: References: Comments: In-reply-to Clive Page message dated "Fri, 02 Apr 2004 15:55:26 +0100" Date: Fri, 02 Apr 2004 10:46:26 -0500 Message-ID: <27943.1080920786@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/11 X-Sequence-Number: 6311 Clive Page writes: > This executes, it need hardly be said, a whole lot faster. Could we see EXPLAIN ANALYZE output? The estimated costs for the two cases are nearly the same, which says to me that there's something wrong with the cost model for r-tree lookups, but I don't know what it is. regards, tom lane