X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 5729E9DCDD1 for ; Sun, 15 Jan 2006 18:28:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 72991-05 for ; Sun, 15 Jan 2006 18:28:33 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.mailpen.net (mail.mailpen.net [66.235.70.248]) by postgresql.org (Postfix) with ESMTP id C69079DCDBF for ; Sun, 15 Jan 2006 18:28:28 -0400 (AST) Received: from athlon1.internal.mailpen.net (pool-71-113-18-74.sttlwa.dsl-w.verizon.net [71.113.18.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mailpen.net (Postfix) with ESMTP id E4C3D17 for ; Sun, 15 Jan 2006 14:28:30 -0800 (PST) Received: from [192.168.128.199] (TpA22p1.internal.mailpen.net [192.168.128.199]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by athlon1.internal.mailpen.net (Postfix) with ESMTP id B0BDA6DC060 for ; Sun, 15 Jan 2006 14:28:29 -0800 (PST) Message-ID: <43CACC78.7090107@ultimeth.com> Date: Sun, 15 Jan 2006 14:28:08 -0800 From: "Dean Gibson (DB Administrator)" Organization: UltiMeth Systems User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: pgsql-sql Subject: Re: What does "merge-joinable join conditions" mean ???? References: <43CAAFA6.6050001@ultimeth.com> <20060115215448.GA30809@winnie.fuhr.org> In-Reply-To: <20060115215448.GA30809@winnie.fuhr.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.12 required=5 tests=[AWL=0.120] X-Spam-Score: 0.12 X-Spam-Level: X-Archive-Number: 200601/82 X-Sequence-Number: 23871 On 2006-01-15 13:54, Michael Fuhr wrote: > What's the query? > SELECT count(*) FROM "GenAppExtra" FULL JOIN "GeoRestrict" ON callsign ~ pattern WHERE region_id = 4 OR geo_region = 4; If either of the "region_id = 4" (a field in the right-hand table) or "geo_region = 4" (a field in the left-hand table) are removed, the SELECT functions (does not give an error message), as does the case where the "callsign ~ pattern" (one field is from each table) is replaced by "callsign = pattern". What's frustrating is that both tables are small, and "GeoRestrict" is only about 15 rows. At this point, I'm considering a UNION; alternate suggestions welcome! -- Dean