| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Franck Routier <franck(dot)routier(at)axege(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: What happens between end of explain analyze and end of query execution ? |
| Date: | 2013-04-05 14:17:28 |
| Message-ID: | 4113.1365171448@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Franck Routier <franck(dot)routier(at)axege(dot)com> writes:
> Le 04/04/2013 21:08, Tom Lane a crit :
>> Hmph. Can't see any reason for that to take a remarkably long time to
>> plan. Can you put together a self-contained test case demonstrating
>> excessive planning time? What PG version is this, anyway?
> What I notice is that removing joins has a huge impact on the time
> explain takes to return:
Hm, kind of looks like it's just taking an unreasonable amount of time
to process each join clause. What have you got the statistics targets
set to in this database? What are the datatypes of the join columns?
And (again) what PG version is this exactly?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2013-04-05 14:17:45 | Re: What happens between end of explain analyze and end of query execution ? |
| Previous Message | Franck Routier | 2013-04-05 13:55:08 | Re: What happens between end of explain analyze and end of query execution ? |