pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Pryscila B Guttoski <pryscila.lista@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: About method of PostgreSQL's Optimizer
Date: Tue, 13 Sep 2005 21:40:45 -0300
Message-ID: <cf0868bd0509131740335e27ab@mail.gmail.com> (raw)
In-Reply-To: <43275DCA.7040006@samurai.com>
References: <cf0868bd05091315503024742@mail.gmail.com>
	<43275DCA.7040006@samurai.com>

Thank's guys!
I'll send to pgsql-hackers...

[]'s
Pryscila

On 9/13/05, Neil Conway <neilc@samurai.com> wrote:
> 
> Pryscila B Guttoski wrote:
> > On my master course, I'm studying the PostgreSQL's optimizer.
> > I don't know if anyone in this list have been participated from the
> > PostgreSQL's Optimizer development, but maybe someone can help me on 
> this
> > question.
> 
> pgsql-hackers might be more appropriate.
> 
> > PostgreSQL generates all possible plans of executing the query (using an
> > almost exhaustive search), then gives a cost to each plan and finally 
> the
> > cheapest one is selected for execution.
> > There are other methods for query optimization, one of them is based on 
> plan
> > transformations (for example, using A-Star algorithm) instead of plan
> > constructions used by PostgreSQL.
> 
> Right, the main query planner uses a nearly-exhaustive search. For
> queries with many joins (when the cost of an exhaustive search would be
> prohibitive), "GEQO" is used, which uses a genetic algorithm to avoid an
> exhaustive search of the solution space.
> 
> > Does anyone know why this method was choosen?
> 
> As far as I know, the main planner algorithm is fairly standard and is
> mainly different from System R's canonical algorithm in the details,
> like whether non-left-deep plans are pruned.
> 
> > Are there any papers or researches about it?
> 
> There are many papers on the System R algorithm and similar techniques,
> which should explain the basic motivations for the design. I'm not aware
> of any papers specifically on the PostgreSQL query optimizer, although
> there have been a few presentations on it:
> 
> http://neilc.treehou.se/optimizer.pdf
> http://conferences.oreillynet.com/presentations/os2003/lane_tom.pdf
> 
> -Neil
>

view thread (16+ messages)  latest in thread

Message-ID: <cf0868bd0509131740335e27ab@mail.gmail.com>
Permalink:  ../cf0868bd0509131740335e27ab@mail.gmail.com/
Also on:    postgresql.org/message-id/cf0868bd0509131740335e27ab@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pryscila.lista@gmail.com
  Subject: Re: About method of PostgreSQL's Optimizer
  In-Reply-To: <cf0868bd0509131740335e27ab@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox