X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id BEE02D1B436 for ; Fri, 28 Nov 2003 19:19:36 +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 82681-07 for ; Fri, 28 Nov 2003 15:19:06 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 9B1BAD1B472 for ; Fri, 28 Nov 2003 15:19:04 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hASJIk19029785; Fri, 28 Nov 2003 14:18:47 -0500 (EST) To: Tomasz Myrta Cc: Lista dyskusyjna pgsql-sql Subject: Re: explicit joins wrong planning In-reply-to: <3FC63057.3080009@klaster.net> References: <3FC63057.3080009@klaster.net> Comments: In-reply-to Tomasz Myrta message dated "Thu, 27 Nov 2003 18:11:51 +0100" Date: Fri, 28 Nov 2003 14:18:46 -0500 Message-ID: <29784.1070047126@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/311 X-Sequence-Number: 16126 Tomasz Myrta writes: > Postgres doesn't use join on these both fields and doesn't use index > scan properly. Hard to say much when you didn't actually show us the output of EXPLAIN ANALYZE. regards, tom lane