Re: Simple join optimized badly?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Mark Kirkwood <markir@xxxxxxxxxxxxxxx>
Subject: Re: Simple join optimized badly?
From: Mark Kirkwood <markir@xxxxxxxxxxxxxxx>
Date: Wed, 11 Oct 2006 13:36:39 +1300
Cc: "Jim C. Nasby" <jim@xxxxxxxxx>, Chris Browne <cbbrowne@xxxxxxx>, pgsql-performance@xxxxxxxxxxxxxx
In-reply-to: <452C3C2D.6000008@xxxxxxxxxxxxxxx>
References: <45274A77.7080005@xxxxxxxxxxxxxxxx> <18722.1160236300@xxxxxxxxxxxxx> <5f820f750610071850o6ed0b19o162d65d1987b2a8c@xxxxxxxxxxxxxx> <200610081605.03501.josh@xxxxxxxxxxxx> <4529A0CA.8000904@xxxxxxxxxxxxxxxx> <4529B6D0.2010206@xxxxxxxxxxxxxxx> <4529B7E8.8080606@xxxxxxxxxxxxxxxx> <604pud8ise.fsf@xxxxxxxxxxxxxxxxxxxxxxx> <20061009211827.GL72517@xxxxxxxxx> <452C3C2D.6000008@xxxxxxxxxxxxxxx>
User-agent: Thunderbird 1.5.0.7 (X11/20061003)

Mark Kirkwood wrote:

who believe it is possible to build a "start enough" optimizer.

That's meant to read "smart enough" optimizer .. sorry.

References:
- Simple join optimized badly?
  - From: Craig A. James
- Re: Simple join optimized badly?
  - From: Tom Lane
- Re: Simple join optimized badly?
  - From: Denis Lussier
- Re: Simple join optimized badly?
  - From: Josh Berkus
- Re: Simple join optimized badly?
  - From: Craig A. James
- Re: Simple join optimized badly?
  - From: Mark Kirkwood
- Re: Simple join optimized badly?
  - From: Craig A. James
- Re: Simple join optimized badly?
  - From: Chris Browne
- Re: Simple join optimized badly?
  - From: Jim C. Nasby
- Re: Simple join optimized badly?
  - From: Mark Kirkwood

Prev by Date: Re: Simple join optimized badly?
Next by Date: Re: Scrub one large table against another
Previous by thread: Re: Simple join optimized badly?
Next by thread: Re: Simple join optimized badly?
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux