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

bootstrap

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Tom Lane authored
    The CHECK_IS_BINARY_UPGRADE macro is not sufficient security protection
    if we're going to dereference pass-by-reference arguments before it.
    
    But in any case we really need to explicitly check PG_ARGISNULL for all
    the arguments of a non-strict function, not only the ones we expect null
    values for.
    
    Oversight in commits 30982be4 and
    f92fc4c9.  Found by Andreas Seltenreich.
    (The other usages in pg_upgrade_support.c seem safe.)
    939d10cd
    History
    Name Last commit Last update
    ..