X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 80C6F9FA13E for ; Tue, 13 Jun 2006 18:07:34 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 30044-01 for ; Tue, 13 Jun 2006 18:07:25 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id B55159F9316 for ; Tue, 13 Jun 2006 18:07:25 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k5DL7Osq010558; Tue, 13 Jun 2006 17:07:24 -0400 (EDT) To: "Shaun Thomas" cc: pgsql-performance@postgresql.org Subject: Re: Confirmation of bad query plan generated by 7.4 tree In-reply-to: <448EDFC4.8F27.00A9.0@leapfrogonline.com> References: <448EB053.8F27.00A9.0@leapfrogonline.com><448EB053.8F27.00A9.0@leapfrogonline.com> <9119.1150222168@sss.pgh.pa.us> <448EDFC4.8F27.00A9.0@leapfrogonline.com> Comments: In-reply-to "Shaun Thomas" message dated "Tue, 13 Jun 2006 15:54:44 -0500" Date: Tue, 13 Jun 2006 17:07:24 -0400 Message-ID: <10557.1150232844@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/206 X-Sequence-Number: 19563 "Shaun Thomas" writes: > Simply changing: > now() - interval '2 days' > to > '2006-06-11 15:30:00' > generated a much more accurate set of estimates. Yeah, 7.4 won't risk basing estimates on the results of non-immutable functions. We relaxed that in 8.0 I believe. regards, tom lane