From: Gerardo Herzig <gherzig@fmed.uba.ar>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: plpythonu and "hello concurrent world"
Date: Wed, 05 Dec 2007 12:19:42 -0300
Message-ID: <4756C18E.2030608@fmed.uba.ar> (raw)
In-Reply-To: <21003.1196865724@sss.pgh.pa.us>
References: <4756A32A.9020101@fmed.uba.ar>
<21003.1196865724@sss.pgh.pa.us>
Tom Lane wrote:
>Gerardo Herzig <gherzig@fmed.uba.ar> writes:
>
>
>>Hi all. Im having some "problems" with a small concurrent plpython function.
>>
>>
>
>Don't even *think* about starting multiple threads inside the Postgres
>backend. It's an excellent way to break things.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>
>
>
>
Damn!! Well, comming from you Tom, i guess i will just look for another
approach without complaining ^^.
Thanks!
Gerardo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gherzig@fmed.uba.ar, tgl@sss.pgh.pa.us
Subject: Re: plpythonu and "hello concurrent world"
In-Reply-To: <4756C18E.2030608@fmed.uba.ar>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox