Re: What happens if I create new threads from within a postgresql function? - Mailing list pgsql-general

From Bruce Momjian
Subject Re: What happens if I create new threads from within a postgresql function?
Date
Msg-id 20130218150258.GK12029@momjian.us
Whole thread Raw
In response to Re: What happens if I create new threads from within a postgresql function?  (Seref Arikan <serefarikan@kurumsalteknoloji.com>)
Responses Re: What happens if I create new threads from within a postgresql function?  (Seref Arikan <serefarikan@kurumsalteknoloji.com>)
List pgsql-general
On Mon, Feb 18, 2013 at 02:51:13PM +0000, Seref Arikan wrote:
> Thanks Bruce,
> I too think that it should be fine, as long as I make sure that the spawned
> threads do not call back to originating thread and they are properly terminated
> once they're finished etc.
> Various messages I've seen in the list archives seem to mention that spawning
> threads is a bad idea, etc etc. I just could not find a technical discussion of
> why this is a bad idea. Maybe I have failed to generate the correct search
> terms.
> It would be great to know why and when this would be a dangerous thing  to do.

The problem comes with calling Postgres subsystems from multiple
threads, which it doesn't sound like you are doing.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-general by date:

Previous
From: Seref Arikan
Date:
Subject: Re: What happens if I create new threads from within a postgresql function?
Next
From: Seref Arikan
Date:
Subject: Re: What happens if I create new threads from within a postgresql function?