Received: from sss.pgh.pa.us ([216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3D33v808179 for ; Thu, 12 Apr 2001 23:03:57 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f3D33TR02095; Thu, 12 Apr 2001 23:03:29 -0400 (EDT) To: Kyle cc: pgsql-sql@postgresql.org Subject: Re: Update In-reply-to: <3ACF5E6C.51106D1C@actarg.com> References: <3ACF5E6C.51106D1C@actarg.com> Comments: In-reply-to Kyle message dated "Sat, 07 Apr 2001 12:37:32 -0600" Date: Thu, 12 Apr 2001 23:03:29 -0400 Message-ID: <2092.987131009@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200104/189 X-Sequence-Number: 2539 Kyle writes: > It appears that the first function would get evaluated first under 7.0.3 > but the last function gets evaluated first under 7.1. Is that accurate? Actually, I was under the impression that (all else being equal) WHERE clauses would get evaluated right-to-left in 7.0.* as well. I was meaning to figure out where the clause order reversal is happening and undo it, but didn't get around to it for 7.1. > Is there a way to control which functions are given precidence? Nope, not at the moment. The code has remnants of a notion of cost of evaluation for functions, but it's not being used for anything ... regards, tom lane