From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, jonah(dot)harris(at)gmail(dot)com |
Cc: | pryscila(dot)lista(at)gmail(dot)com |
Subject: | Re: About method of PostgreSQL's Optimizer |
Date: | 2005-09-14 15:44:02 |
Message-ID: | 200509140844.03449.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
Pryscila,
> > 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.
We do certainly need a specific optimization for large star-schema joins. I'm
not certain that A* is suitable for our cost model, though; I think we might
need to work up something more particular to Postgres.
> > Does anyone know why this method was choosen? Are there any papers or
> > researches about it?
There probably are on ACM but I've not read them. Ours is a pretty
straightforward implementation of a cost-based optimizer. You can always
read the code ;-)
Mark Kirkwood put together this nice paper on planner statistics:
http://www.powerpostgresql.com/PlanStats
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Pryscila B Guttoski | 2005-09-14 15:52:50 | Re: About method of PostgreSQL's Optimizer |
Previous Message | Andreas Pflug | 2005-09-14 14:49:01 | Re: 8.1 system info / admin functions |
From | Date | Subject | |
---|---|---|---|
Next Message | Pryscila B Guttoski | 2005-09-14 15:52:50 | Re: About method of PostgreSQL's Optimizer |
Previous Message | Kevin Grittner | 2005-09-14 14:23:22 | Re: Low performance on Windows problem |