From: Shaun Thomas <sthomas@leapfrogonline.com>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Confirmation of bad query plan generated by 7.4
Date: Tue, 13 Jun 2006 17:41:06 -0500
Message-ID: <448EF8B2.8F27.00A9.0@leapfrogonline.com> (raw)
In-Reply-To: <20060613215418.GI34196@pervasive.com>
References: <9119.1150222168@sss.pgh.pa.us>
<448EDFC4.8F27.00A9.0@leapfrogonline.com>
<20060613211347.GB34196@pervasive.com>
<448EE95D.8F27.00A9.0@leapfrogonline.com>
<20060613215418.GI34196@pervasive.com>
>>> On 6/13/2006 at 4:54 PM, "Jim C. Nasby" <jnasby@pervasive.com>
wrote:
> SELECT attname, attstattarget
> FROM pg_attribute
> WHERE attrelid='table_name'::regclass AND attnum >= 0;
-1 for all values.
> SHOW default_statistics_target;
10.
Here's something slightly annoying: I tried precalculating the value
in my stored proc, and it's still ignoring it.
lastTime := now() - interval ''7 days'';
UPDATE fact_credit_app
SET activated_date_id = ad.date_id
FROM l_event_log e
JOIN c_event_type t ON (t.id = e.event_type_id)
JOIN wf_date ad ON (e.event_date::date=ad.datestamp)
WHERE e.ext_id=fact_credit_app.unique_id
AND t.event_name = ''activation''
AND e.event_date > lastTime
AND fact_credit_app.activated_date_id IS NULL;
Instead of taking a handful of seconds (like when I replace
lastTime with the text equivalent), it takes 10 minutes...
I can see the planner not liking the results of a function,
but a variable? That's a static value! ::cry::
--
Shaun Thomas
Database Administrator
Leapfrog Online
807 Greenwood Street
Evanston, IL 60201
Tel. 847-440-8253
Fax. 847-570-5750
www.leapfrogonline.com
Confidentiality Note:
The document(s) accompanying this e-mail transmission, if any, and the
e-mail transmittal message contain information from Leapfrog Online
Customer Acquisition, LLC is confidential or privileged. The information
is intended to be for the use of the individual(s) or entity(ies) named
on this e-mail transmission message. If you are not the intended
recipient, be aware that any disclosure, copying, distribution or use of
the contents of this e-mail is prohibited. If you have received this
e-mail in error, please immediately delete this e-mail and notify us by
telephone of the error
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sthomas@leapfrogonline.com, jnasby@pervasive.com, tgl@sss.pgh.pa.us
Subject: Re: Confirmation of bad query plan generated by 7.4
In-Reply-To: <448EF8B2.8F27.00A9.0@leapfrogonline.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox