| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Noah Misch <noah(at)leadboat(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Kohei(dot)Kaigai(at)emea(dot)nec(dot)com, thom(at)linux(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [v9.2] Fix Leaky View Problem |
| Date: | 2011-10-19 03:08:04 |
| Message-ID: | 2199.1318993684@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Oct 16, 2011 at 4:46 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
>> I tried to reproduce the scenario with enough small from/join_collapse_limit
>> (typically 1), but it allows to push down qualifiers into the least scan plan.
> Hmm, you're right. LIMIT 1000000000 prevents qual pushdown, but
> hitting from_collapse_limit/join_collapse_limit apparently doesn't. I
> could have sworn I've seen this work the other way, but I guess not.
No, the collapse_limit variables are entirely unrelated to subquery
flattening, or to qual pushdown for that matter. They only restrict the
number of join paths we consider. And we will attempt to push down
quals into an unflattened subquery, too, if it looks safe. See
subquery_is_pushdown_safe, qual_is_pushdown_safe, etc in allpaths.c.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-10-19 03:27:42 | Re: termination of backend waiting for sync rep generates a junk log message |
| Previous Message | Jun Ishiduka | 2011-10-19 02:47:08 | Re: Online base backup from the hot-standby |