| From: | Ow Mun Heng <Ow(dot)Mun(dot)Heng(at)wdc(dot)com> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | Dave Dutcher <dave(at)tridecap(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: PostgreSQL vs MySQL, and FreeBSD |
| Date: | 2007-11-19 01:27:47 |
| Message-ID: | 1195435667.11620.5.camel@neuromancer.home.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 2007-11-16 at 11:06 -0500, Jonah H. Harris wrote:
> On Nov 16, 2007 10:56 AM, Dave Dutcher <dave(at)tridecap(dot)com> wrote:
> > I don't know about that. There are times when it is the right plan:
>
> Agreed. IMHO, there's nothing wrong with nested-loop join as long as
> it's being used properly.
I do agree also, but in some other cases, the usage of nested loops (esp
when the number of rows estimated to be returned vs the actual number of
rows being returned differs by up to 100x (or more) then it becomes a
major issue.
The example pointed out by Dave D shows the est rows = 1 and actual
rows=1, then good performance of course.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Decibel! | 2007-11-19 04:08:40 | Re: autovacuum: recommended? |
| Previous Message | Dean Rasheed | 2007-11-18 22:13:58 | RE: Performance problem (outer join + view + non-strict functions) |