Re: Parallell Optimizer - Mailing list pgsql-hackers

From Fred&Dani&Pandora&Aquiles
Subject Re: Parallell Optimizer
Date
Msg-id CACcJavBYROct5SU=W6iFWK+tW7xDWfoWDGuGMyG2JDJRN0coSw@mail.gmail.com
Whole thread Raw
In response to Re: Parallell Optimizer  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Parallell Optimizer  (Hannu Krosing <hannu@2ndQuadrant.com>)
List pgsql-hackers
Hi,
 
>> 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?


Well, there are versions of genetic algorithms that use the concept of islands in which the populations evolve in parallel in the different islands and allows interaction between the islands and so on. I'm working in an algorithm based on multiagent systems. At the present moment, I mean in H2, the agents are threads, there are a few locks related to agents solutions, and a few locks for the best current solution in the environment where the agents are 'running'. The agents can exchange messages with a purpose. The environment is shared by the all agents and they use the environment to get informations from another agents (current solution for example), tries to update the best current solution and so on.

According with the answers, I think the feature Background Worker Processes still doesn't meets my needs. So, I'll keep monitoring the progress of this functionality to implement the planner in future.

Thanks,

Fred


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Freezing without write I/O
Next
From: Peter Eisentraut
Date:
Subject: Re: Revisit items marked 'NO' in sql_features.txt