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

src

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Robert Haas authored
    This was always intended to work, but due to an oversight in
    max_parallel_hazard_walker, it didn't.  In testing, we missed the
    fact that it was only working for custom plans, where the parameter
    value has been substituted for the parameter itself early enough
    that everything worked.  In a generic plan, the Param node survives
    and must be treated as parallel-safe.  SerializeParamList provides
    for the transmission of parameter values to workers.
    
    Amit Kapila with help from Kuntal Ghosh.  Some changes by me.
    
    Discussion: http://postgr.es/m/CAA4eK1+_BuZrmVCeua5Eqnm4Co9DAXdM5HPAOE2J19ePbR912Q@mail.gmail.com
    a87c0c76
    History
    Name Last commit Last update
    ..