Re: Yet another slow nested loop
| От | Alexander Staubo |
|---|---|
| Тема | Re: Yet another slow nested loop |
| Дата | |
| Msg-id | 88daf38c0906160658m23cdf97fs71d303a4415d6225@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Yet another slow nested loop ("Dave Dutcher" <dave@tridecap.com>) |
| Список | pgsql-performance |
On Tue, Jun 16, 2009 at 3:56 PM, Dave Dutcher<dave@tridecap.com> wrote: >> -----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? No. > 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. The default, ie. 4.0. A.
В списке pgsql-performance по дате отправления: