Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

execParallel.c

Blame
    • Robert Haas's avatar
      3bd909b2
      Add a Gather executor node. · 3bd909b2
      Robert Haas authored
      A Gather executor node runs any number of copies of a plan in an equal
      number of workers and merges all of the results into a single tuple
      stream.  It can also run the plan itself, if the workers are
      unavailable or haven't started up yet.  It is intended to work with
      the Partial Seq Scan node which will be added in future commits.
      
      It could also be used to implement parallel query of a different sort
      by itself, without help from Partial Seq Scan, if the single_copy mode
      is used.  In that mode, a worker executes the plan, and the parallel
      leader does not, merely collecting the worker's results.  So, a Gather
      node could be inserted into a plan to split the execution of that plan
      across two processes.  Nested Gather nodes aren't currently supported,
      but we might want to add support for that in the future.
      
      There's nothing in the planner to actually generate Gather nodes yet,
      so it's not quite time to break out the champagne.  But we're getting
      close.
      
      Amit Kapila.  Some designs suggestions were provided by me, and I also
      reviewed the patch.  Single-copy mode, documentation, and other minor
      changes also by me.
      3bd909b2
      History
      Add a Gather executor node.
      Robert Haas authored
      A Gather executor node runs any number of copies of a plan in an equal
      number of workers and merges all of the results into a single tuple
      stream.  It can also run the plan itself, if the workers are
      unavailable or haven't started up yet.  It is intended to work with
      the Partial Seq Scan node which will be added in future commits.
      
      It could also be used to implement parallel query of a different sort
      by itself, without help from Partial Seq Scan, if the single_copy mode
      is used.  In that mode, a worker executes the plan, and the parallel
      leader does not, merely collecting the worker's results.  So, a Gather
      node could be inserted into a plan to split the execution of that plan
      across two processes.  Nested Gather nodes aren't currently supported,
      but we might want to add support for that in the future.
      
      There's nothing in the planner to actually generate Gather nodes yet,
      so it's not quite time to break out the champagne.  But we're getting
      close.
      
      Amit Kapila.  Some designs suggestions were provided by me, and I also
      reviewed the patch.  Single-copy mode, documentation, and other minor
      changes also by me.