| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Markus Schiltknecht <markus(at)bluegap(dot)ch>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Support Parallel Query Execution in Executor |
| Date: | 2006-04-11 18:06:27 |
| Message-ID: | 20060411180627.GQ11760@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Greg Stark wrote:
> Even on Solaris I'm sure parsing and preparing plans for all the queries,
> building up the system table cache for all the objects in the database, and so
> on are much much more expensive than fork(). I wouldn't be surprised if even
> on windows it was still a pretty close race.
Parsing/planning what queries? Regarding system caches, they are
populated from a cache file; they are not read from the catalogs each
time.
But while we don't see a patch implementing the idea, this is all very
theoretical and probably wrong.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonah H. Harris | 2006-04-11 18:07:35 | Re: adding fields to pg_database |
| Previous Message | Greg Stark | 2006-04-11 18:00:41 | Re: Support Parallel Query Execution in Executor |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-04-11 18:10:00 | Re: Support Parallel Query Execution in Executor |
| Previous Message | Greg Stark | 2006-04-11 18:00:41 | Re: Support Parallel Query Execution in Executor |