| From: | Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> |
|---|---|
| To: | David Johnston <polobo(at)yahoo(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Can I force a query plan to materialise part? |
| Date: | 2012-10-02 03:22:57 |
| Message-ID: | 506A5E11.90809@strategicdata.com.au |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 02/10/12 12:44, David Johnston wrote:
> On Oct 1, 2012, at 22:33, Toby Corkindale <toby(dot)corkindale(at)strategicdata(dot)com(dot)au> wrote:
>
>> Hi,
>> Is there any way to force the query planner to do a materialisation stage?
>>
>> I have a query that joins two views, and takes 28 seconds to run.
>> However if I create temporary tables that contain the contents of each view, and then join them, the total time is 1.3 seconds.
>>
>> Is there a way to hint to the query planner that it should be taking that approach?
>>
>> Thanks,
>> Toby
>
> Have you tried?
>
> With v1 as (), v2 as () select v1 join v2
Hi David,
I just tried that now, and it ran in 350ms; much faster than even the
temporary-table-creating method.
thanks!
Toby
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Toby Corkindale | 2012-10-02 03:28:32 | Re: Can I force a query plan to materialise part? |
| Previous Message | Ondrej Ivanič | 2012-10-02 03:02:50 | Re: Can I force a query plan to materialise part? |