| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: planner issue with constraint exclusion |
| Date: | 2008-12-16 01:10:06 |
| Message-ID: | 16537.1229389806@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> On Mon, 2008-12-15 at 14:28 -0500, Tom Lane wrote:
>> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>>> Of the functions the only one that will use constraint_exclusion is the
>>> one that explicitly passes the date value.
>>
>> Since you haven't shown us the constraints you're talking about, or the
>> resulting plans, it's difficult for anyone to guess what's going on.
> Check constraints:
> "foo_stats_day_q1_day_check" CHECK (day >= '2007-01-01'::date AND
> day < '2007-04-01'::date)
Well, that certainly looks like constraint exclusion should work with
the EXECUTE case. What leads you to conclude it doesn't?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emmanuel Cecchet | 2008-12-16 02:05:16 | Re: Fwd: [PATCHES] Auto Partitioning Patch - WIP version 1 |
| Previous Message | Tom Lane | 2008-12-16 00:35:38 | Re: [ADMIN] shared_buffers and shmmax |