On 06/01/2010 05:45 AM, Greg Smith wrote:
Two thoughts. First, build a test performance case assuming it will fail
to scale upwards, looking for problems. If you get lucky, great, but
don't assume this will work--it's proven more difficult than is obvious
in the past for others.
Second, if you do end up being throttled by the GIL, you can probably
build a solution for Python 2.6/3.0 using the multiprocessing module for
your use case: http://docs.python.org/library/multiprocessing.html
Thanks, Greg - multiprocessing looks very usable for my application.
Much more than using fork() and pipes myself...
Joachim
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
