Re: Support Parallel Query Execution in Executor
От
Markus Schiltknecht
Тема
Re: Support Parallel Query Execution in Executor
Дата
Msg-id
1144663351.32238.5.camel@fotomarburg
Ответ на
Список
Дерево обсуждения
Re: Support Parallel Query Execution in Executor "Qingqing Zhou" <zhouqq@cs.toronto.edu>
Re: Support Parallel Query Execution in Executor Markus Schiltknecht <markus@bluegap.ch>
Re: Support Parallel Query Execution in Executor Alvaro Herrera <alvherre@commandprompt.com>
Re: Support Parallel Query Execution in Executor Markus Schiltknecht <markus@bluegap.ch>
Re: Support Parallel Query Execution in Executor "Jim C. Nasby" <jnasby@pervasive.com>
Re: Support Parallel Query Execution in Executor Greg Stark <gsstark@mit.edu>
Re: Support Parallel Query Execution in Executor Alvaro Herrera <alvherre@commandprompt.com>
Re: Support Parallel Query Execution in Executor Greg Stark <gsstark@mit.edu>
Re: Support Parallel Query Execution in Executor Alvaro Herrera <alvherre@commandprompt.com>
Re: Support Parallel Query Execution in Executor "Jim C. Nasby" <jnasby@pervasive.com>
Hi, On Sun, 2006-04-09 at 15:11 -0400, Tom Lane wrote: > You can't just retarget a backend to operate in another database, at > least not without major changes in that infrastructure. Why not? What would be needed to retarget a backend to operate in another database? Such a retargetting would be helpful in several cases: - pre-forking of backends (well, depends on efficiency of retargetting..) - slave backends for parallel query execution - slave backends for replaying replicated transactions I'm using backends operating without a client connection, with superuser privileges only. But those are still connected to one specific database. It would really be helpfull if I could retarget them as needed. Regards Markus
В списке pgsql-hackers по дате отправления