Re: a funnel by any other name - Mailing list pgsql-hackers

From Nicolas Barbier
Subject Re: a funnel by any other name
Date
Msg-id CAP-rdTbvzossfActc9jNdtFou4kNQr+JdH2wVbrmtd7jK3BYmg@mail.gmail.com
Whole thread Raw
In response to a funnel by any other name  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: a funnel by any other name
List pgsql-hackers
2015-09-17 Robert Haas <robertmhaas@gmail.com>:

> 1. Exchange Bushy
> 2. Exchange Inter-Operator (this is what's currently implemented)
> 3. Exchange Replicate
> 4. Exchange Merge
> 5. Interchange

> 1. ?
> 2. Gather
> 3. Broadcast (sorta)
> 4. Gather Merge
> 5. Redistribute

> 1. Parallel Child
> 2. Parallel Gather
> 3. Parallel Replicate
> 4. Parallel Merge
> 5. Parallel Redistribute

FYI, SQL Server has these in its execution plans:

* Distribute Streams: read from one thread, write to multiple threads
* Repartition Streams: both read and write from/to multiple threads
* Gather Streams: read from multiple threads, write to one thread

Nicolas

-- 
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: On-demand running query plans using auto_explain and signals
Next
From: Amit Kapila
Date:
Subject: Re: Parallel Seq Scan