From: | "Fred&Dani&Pandora&Aquiles" <fred(at)nti(dot)ufop(dot)br> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Parallell Optimizer |
Date: | 2013-06-07 17:09:57 |
Message-ID: | CACcJavBKgtZiTLOpKZrMprSvD7_St-Hp58khUPZec3-DBFhL4g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I asked a while ago in this group about the possibility to implement a
parallel planner in a multithread way, and the replies were that the
proposed approach couldn't be implemented, because the postgres is not
thread-safe. With the new feature Background Worker Processes, such
implementation would be possible? If yes, do you can see possible problems
in implement this approach, for example, the bgprocess can't access some
planning core functions like make_join_rel, acess them in parallel and so
on. I want start a research to work in a parallel planner in postgres, I
succeeded in in the DBMS H2, but my first option still is the postgres, and
any help is welcome.
Att,
Fred
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2013-06-07 17:11:41 | Re: SPGist "triple parity" concept doesn't work |
Previous Message | Robert Haas | 2013-06-07 17:01:00 | Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken |