Search Postgresql Archives

Re: What happens if I create new threads from within a postgresql function?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Feb 18, 2013 at 10:33:26PM +0530, Atri Sharma wrote:
> >> While your threads are executing, your query can't be cancelled --
> >> only a hard kill will take the database down.  If you're ok with that
> >> risk, then go for it.  If you're not, then I'd thinking about
> >> sendinging the bytea through a protocol to a threaded processing
> >> server running outside of the database.  More work and slower
> >> (protocol overhead), but much more robust.
> > 
> > You can see the approach of not calling any PG-specific routines from
> > theads here:
> > 
> >    http://wiki.postgresql.org/wiki/Parallel_Query_Execution#Approaches
> > 
> 
> 
> Is there any way to locally synchronise the threads in my code,and
> send the requests to the PostgreSQL backend one at a time? Like a waiting
> queue in my code?

Is this from the client code?  That is easy from libpq using
asynchronous queries.

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

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


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux