From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | michael(dot)paquier(at)gmail(dot)com |
Cc: | simon(at)2ndquadrant(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, robertmhaas(at)gmail(dot)com, fred(at)nti(dot)ufop(dot)br, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Parallell Optimizer |
Date: | 2013-06-11 00:45:28 |
Message-ID: | 20130611.094528.83183479329987568.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Sat, Jun 8, 2013 at 5:04 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>
>> On 7 June 2013 20:23, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> > As for other databases, I suspect that ones that have parallel execution
>> > are probably doing it with a thread model not a process model.
>>
>> Separate processes are more common because it covers the general case
>> where query execution is spread across multiple nodes. Threads don't
>> work across nodes and parallel queries predate (working) threading
>> models.
>>
> Indeed. Parallelism based on processes would be more convenient for
> master-master
> type of applications. Even if no master-master feature is implemented
> directly in core,
> at least a parallelism infrastructure based on processes could be used for
> this purpose.
As long as "true" synchronous replication is not implemented in core,
I am not sure there's a value for parallel execution spreading across
multile nodes because of the delay of data update propagation.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2013-06-11 00:49:13 | Re: Parallell Optimizer |
Previous Message | Michael Paquier | 2013-06-11 00:37:59 | Re: Parallell Optimizer |