| From: | "Dave Dutcher" <dave(at)tridecap(dot)com> |
|---|---|
| To: | "'Alexander Staubo'" <alex(at)bengler(dot)no>, "'pgsql-performance'" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Yet another slow nested loop |
| Date: | 2009-06-16 13:56:38 |
| Message-ID: | 409535A69D444132B8EA07528E1EFF9B@tridecap.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> -----Original Message-----
> From: Alexander Staubo
>
> -> Nested Loop (cost=0.00..5729774.95 rows=10420 width=116)
> (actual time=262614.470..262614.470 rows=0 loops=1)
> Join Filter: ((photos.taken_at > (event_instances."time" +
> '-01:00:00'::interval)) AND (photos.taken_at < (event_instances."time"
> + '07:00:00'::interval)))
> -> Nested Loop (cost=0.00..2055574.35 rows=11869630
> width=120) (actual time=21.750..121838.012 rows=14013998 loops=1)
Do you have any of the other enable_* options set to false? What do you
have random_page_cost set to? I ask because I'm surprised to see postgres
choose to loop when it knows it will have to loop 11 million times.
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Staubo | 2009-06-16 13:58:35 | Re: Yet another slow nested loop |
| Previous Message | Alexander Staubo | 2009-06-16 13:45:33 | Yet another slow nested loop |