Re: Re: [GENERAL] postgreSQL multithreading - Mailing list pgsql-general

From Craig Ringer
Subject Re: Re: [GENERAL] postgreSQL multithreading
Date
Msg-id 47EFCD10.6080303@postnewspapers.com.au
Whole thread Raw
In response to Re: [GENERAL] postgreSQL multithreading  (postgre@seznam.cz)
Responses Re: [GENERAL] Re: [GENERAL] postgreSQL multithreading  (postgre@seznam.cz)
List pgsql-general
postgre@seznam.cz wrote:
>
> What about some C dynamically loaded function in which I could call new connection for each thread?
>
Past discussion here suggests that the backends are strictly single
threaded. While you might be able to use multiple threads - I don't know
- I expect you'd need to protect all SPI access by a lock that
serialized everything anyway.

Doing it externally with a script / program that uses multiple
connections might just be the way. Unfortunately that means that you
don't get a single consistent snapshot - each connection will have its
own, potentially different, view of the database state.

A possible use for read only transactions being able to share a snapshot
came up in discussion a few weeks ago. I guess this is another one.

--
Craig Ringer

pgsql-general by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Survey: renaming/removing script binaries (createdb, createuser...)
Next
From: "A. Kretschmer"
Date:
Subject: Re: Re: [GENERAL] postgreSQL multithreading