From: | "Cristian Prieto" <cristian(at)clickdiario(dot)com> |
---|---|
To: | <pryscila(dot)lista(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: About method of PostgreSQL's Optimizer |
Date: | 2005-09-13 23:31:54 |
Message-ID: | 013601c5b8bb$564f7450$6500a8c0@gt.ClickDiario.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
I know you almost had read this, but I think it is a good paper to start with...
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 -----
From: Pryscila B Guttoski
To: pgsql-performance(at)postgresql(dot)org
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.
Does anyone know why this method was choosen? Are there any papers or researches about it?
Thank's a lot,
Pryscila.
From | Date | Subject | |
---|---|---|---|
Next Message | Min Xu (Hsu) | 2005-09-13 23:32:02 | Re: Spinlocks, yet again: analysis and proposed patches |
Previous Message | Joshua D. Drake | 2005-09-13 23:23:02 | Re: About method of PostgreSQL's Optimizer |
From | Date | Subject | |
---|---|---|---|
Next Message | Cristian Prieto | 2005-09-13 23:34:36 | Any other idea for better performance? |
Previous Message | Joshua D. Drake | 2005-09-13 23:23:02 | Re: About method of PostgreSQL's Optimizer |