| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Seref Arikan <serefarikan(at)kurumsalteknoloji(dot)com> |
| Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: What happens if I create new threads from within a postgresql function? |
| Date: | 2013-02-18 15:02:58 |
| Message-ID: | 20130218150258.GK12029@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Seref Arikan | 2013-02-18 15:08:26 | Re: What happens if I create new threads from within a postgresql function? |
| Previous Message | Seref Arikan | 2013-02-18 14:51:13 | Re: What happens if I create new threads from within a postgresql function? |