Re: APR 1.0 released - Mailing list pgsql-hackers

From Sailesh Krishnamurthy
Subject Re: APR 1.0 released
Date
Msg-id mjqd60qhykq.fsf@cs.berkeley.edu
Whole thread Raw
In response to Re: APR 1.0 released  (Christopher Browne <cbbrowne@acm.org>)
Responses Re: APR 1.0 released  ("Jim C. Nasby" <decibel@decibel.org>)
List pgsql-hackers
>>>>> "CB" == Christopher Browne <cbbrowne@acm.org> writes:
   CB> futile discussions ask for it.  Notably, on an SMP system, it   CB> would be a neat idea for complex queries
involvingjoins to   CB> split themselves so that different parts run in separate   CB> threads.
 

You don't really need threads for this. All you need is to have
multiple backends and use queues to exchange tuples at specific
points. This is much like the Exchange operator in Volcano. 
   CB> The other Way, Way Cool part would be for queries that are   CB> scanning big tables to split the scans into
unionsof partial   CB> scans, so that on an 8 CPU box you'd take the "Big 4GB Table"   CB> and have 8 threads
simultaneouslyscanning different parts of   CB> it.  (And making ARC all the more important :-).)
 

Again this can be done without threads .. you just need inter-process
communication. 

(BTW, there is at least one commercial system that follows exactly
this model).

-- 
Pip-pip
Sailesh
http://www.cs.berkeley.edu/~sailesh




pgsql-hackers by date:

Previous
From: Satoshi Nagayasu
Date:
Subject: Re: CREATE OR REPLACE TRIGGER not supported?
Next
From: "Merlin Moncure"
Date:
Subject: pg_locks view and user locks