From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
Date: Thu, 23 Mar 2006 21:22:34 -0500
Message-ID: <87hd5olgyd.fsf@wolfe.cbbrowne.com> (raw)
References: <65f9ddfb0603222219r1742c2aevda37acd55ca845be@mail.gmail.com>
<1143131901.17999.67.camel@state.g2switchworks.com>
<4422D033.2030407@commandprompt.com>
<1143133364.17999.77.camel@state.g2switchworks.com>
Martha Stewart called it a Good Thing when smarlowe@g2switchworks.com (Scott Marlowe) wrote:
> On Thu, 2006-03-23 at 10:43, Joshua D. Drake wrote:
>> > Has someone been working on the problem of splitting a query into pieces
>> > and running it on multiple CPUs / multiple machines? Yes. Bizgress has
>> > done that.
>>
>> I believe that is limited to Bizgress MPP yes?
>
> Yep. I hope that someday it will be released to the postgresql global
> dev group for inclusion. Or at least parts of it.
Question: Does the Bizgress/MPP use threading for this concurrency?
Or forking?
If it does so via forking, that's more portable, and less dependent on
specific complexities of threading implementations (which amounts to
non-portability ;-)).
Most times Jan comes to town, we spend a few minutes musing about the
"splitting queries across threads" problem, and dismiss it again; if
there's the beginning of a "split across processes," that's decidedly
neat :-).
--
output = reverse("moc.liamg" "@" "enworbbc")
http://linuxfinances.info/info/internet.html
Why do we put suits in a garment bag, and put garments in a suitcase?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: cbbrowne@acm.org
Subject: Re: Scaling up PostgreSQL in Multiple CPU / Dual Core
In-Reply-To: <87hd5olgyd.fsf@wolfe.cbbrowne.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox