Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 1D3F24758DA for ; Fri, 26 Apr 2002 18:43:46 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3QMhgF12116; Fri, 26 Apr 2002 18:43:42 -0400 (EDT) To: "Josh Berkus" Cc: pgsql-sql@postgresql.org Subject: Re: Wierd query behaviour In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Fri, 26 Apr 2002 12:38:44 -0700" Date: Fri, 26 Apr 2002 18:43:41 -0400 Message-ID: <12113.1019861021@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/340 X-Sequence-Number: 7604 "Josh Berkus" writes: > UPDATE cases SET status = 99 > WHERE status = 1 AND NOT EXISTS( > SELECT case_id FROM case_clients > WHERE date_resolved IS NULL OR > date_resolved > ((current_date - "interval"('1 year'))::DATE) > and case_clients.case_id = cases.case_id); It says here that OR binds at lower priority than AND. Did you really mean ... WHERE (date_resolved IS NULL OR date_resolved > ((current_date - "interval"('1 year'))::DATE)) and case_clients.case_id = cases.case_id); Since IS NULL isn't indexable, the first version cannot be indexscanned at all. The second version gives you a shot at using the case_clients.case_id index. regards, tom lane