X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id ED032D8DBF
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 13 Sep 2005 20:34:26 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 10811-07
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Tue, 13 Sep 2005 23:34:19 +0000 (GMT)
Received: from mail.clickdiario.com (mail.clickdiario.com [70.85.167.114])
	by svr1.postgresql.org (Postfix) with ESMTP id 65104D8DB5
	for <pgsql-performance@postgresql.org>;
	Tue, 13 Sep 2005 20:34:20 -0300 (ADT)
Received: from localhost (localhost [127.0.0.1])
	by mail.clickdiario.com (Postfix) with ESMTP id 99F1810458;
	Tue, 13 Sep 2005 18:36:58 -0500 (CDT)
Received: from mail.clickdiario.com ([127.0.0.1])
	by localhost (mail.clickdiario.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 20302-05; Tue, 13 Sep 2005 18:36:58 -0500 (CDT)
Received: from cristian (unknown [216.230.158.50])
	by mail.clickdiario.com (Postfix) with ESMTP id 1EC731002D;
	Tue, 13 Sep 2005 18:36:56 -0500 (CDT)
Message-ID: <013601c5b8bb$564f7450$6500a8c0@gt.ClickDiario.local>
From: "Cristian Prieto" <cristian@clickdiario.com>
To: <pryscila.lista@gmail.com>, <pgsql-performance@postgresql.org>
References: <cf0868bd05091315503024742@mail.gmail.com>
Subject: Re: About method of PostgreSQL's Optimizer
Date: Tue, 13 Sep 2005 17:31:54 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0133_01C5B889.088CC240"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at example.com
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.065 required=5 tests=[AWL=-0.031, HTML_50_60=0.095,
	HTML_MESSAGE=0.001]
X-Spam-Level: 
X-Archive-Number: 200509/179
X-Sequence-Number: 14487

This is a multi-part message in MIME format.

------=_NextPart_000_0133_01C5B889.088CC240
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I know you almost had read this, but I think it is a good paper to start =
with...=20

http://lca2005.linux.org.au/Papers/Neil%20Conway/Inside%20the%20PostgreSQ=
L%20Query%20Optimizer/pg_query_optimizer.pdf

Anyway, do you know where could I get more info and theory about =
database optimizer plan? (in general) I like that topic, thanks a lot =
man!
  ----- Original Message -----=20
  From: Pryscila B Guttoski=20
  To: pgsql-performance@postgresql.org=20
  Sent: Tuesday, September 13, 2005 4:50 PM
  Subject: [PERFORM] About method of PostgreSQL's Optimizer


  Hello all!

  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.
  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.=20
  Does anyone know why this method was choosen? Are there any papers or =
researches about it?

  Thank's a lot,
  Pryscila.

------=_NextPart_000_0133_01C5B889.088CC240
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2722" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I know you almost had read this, but I =
think it is=20
a good paper to start with... </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"http://lca2005.linux.org.au/Papers/Neil%20Conway/Inside%20the%20P=
ostgreSQL%20Query%20Optimizer/pg_query_optimizer.pdf">http://lca2005.linu=
x.org.au/Papers/Neil%20Conway/Inside%20the%20PostgreSQL%20Query%20Optimiz=
er/pg_query_optimizer.pdf</A></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Anyway, do you know where could I get =
more info and=20
theory about database optimizer plan? (in general) I like that topic, =
thanks a=20
lot man!</FONT></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A title=3Dpryscila.lista@gmail.com=20
  href=3D"mailto:pryscila.lista@gmail.com">Pryscila B Guttoski</A> =
</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
  title=3Dpgsql-performance@postgresql.org=20
  =
href=3D"mailto:pgsql-performance@postgresql.org">pgsql-performance@postgr=
esql.org</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, September 13, =
2005 4:50=20
  PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [PERFORM] About method =
of=20
  PostgreSQL's Optimizer</DIV>
  <DIV><BR></DIV>Hello all!<BR><BR>On my master course, I'm studying the =

  PostgreSQL's optimizer.<BR>I don't know if anyone in this list have =
been=20
  participated from the PostgreSQL's Optimizer development, but maybe =
someone=20
  can help me on this question.<BR>PostgreSQL generates all possible =
plans of=20
  executing the query (using an almost exhaustive search), then gives a =
cost to=20
  each plan and finally the cheapest one is selected for =
execution.<BR>There are=20
  other methods for query optimization, one of them is based on plan=20
  transformations (for example, using A-Star algorithm) instead of plan=20
  constructions used by PostgreSQL. <BR>Does anyone know why this method =
was=20
  choosen? Are there any papers or researches about it?<BR><BR>Thank's a =

  lot,<BR>Pryscila.<BR></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0133_01C5B889.088CC240--