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

postgres-lambda-diff

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    MinMaxExpr invokes the btree comparison function for its input datatype,
    so it's only leakproof if that function is.  Many such functions are
    indeed leakproof, but others are not, and we should not just assume that
    they are.  Hence, adjust contain_leaked_vars to verify the leakproofness
    of the referenced function explicitly.
    
    I didn't add a regression test because it would need to depend on
    some particular comparison function being leaky, and that's a moving
    target, per discussion.
    
    This has been wrong all along, so back-patch to supported branches.
    
    Discussion: https://postgr.es/m/31042.1546194242@sss.pgh.pa.us
    d6b37cdb
    History
    Name Last commit Last update