| From: | Thomas Mayer <thomas(dot)mayer(at)student(dot)kit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: window function induces full table scan |
| Date: | 2014-01-03 18:25:24 |
| Message-ID: | 52C70094.3040006@student.kit.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Am 03.01.2014 19:04, schrieb Tom Lane:
> I think you need to read the code around subquery_is_pushdown_safe and
> qual_is_pushdown_safe some more.
>
> regards, tom lane
> .
>
In general, I'd need to go throught the pg source code which will take
some time. For instance, I wanted to see which are the requirements for
a patch to be accepted.
Currently, I can't provide you with a patch anyways (lack of time and
knowledge). However, I can possibly give it a try in a few weeks.
If someone is working on that in the meantime, please let me know.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Kolomeitsev | 2014-01-06 05:50:47 | Wrong rows count estimation in query with simple UNION ALL leads to drammatically slow plan |
| Previous Message | Tom Lane | 2014-01-03 18:04:13 | Re: window function induces full table scan |