| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Luis Amigo <lamigo(at)atc(dot)unican(dot)es> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: enable_nestloop |
| Date: | 2001-11-23 20:13:12 |
| Message-ID: | 9881.1006546392@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Luis Amigo <lamigo(at)atc(dot)unican(dot)es> writes:
> if we use set enable_nestloop=off the result is:
> Limit (cost=100160926.76..100160926.76 rows=100 width=120)
> -> Sort (cost=100160926.76..100160926.76 rows=100 width=120)
> -> Nested Loop (cost=100160637.42..100160923.43 rows=100
> width=120)
It's choosing a nestloop at the top level despite the large penalty
added to the cost, presumably because it cannot find any other way to
do the top-level join. You won't get any more useful answer than that
as long as you're not showing us the query and table schemas involved...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | William WAISSE | 2001-11-23 22:42:59 | newbie needs help with postgres internal tables |
| Previous Message | Megalex | 2001-11-23 20:01:06 | Postgresql Not working.. |