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
    Tom Lane authored
    We were using GetConfigOption to collect the old value of each setting,
    overlooking the possibility that it didn't exist yet.  This does happen
    in the case of adding a new entry within a custom variable class, as
    exhibited in bug #6097 from Maxim Boguk.
    
    To fix, add a missing_ok parameter to GetConfigOption, but only in 9.1
    and HEAD --- it seems possible that some third-party code is using that
    function, so changing its API in a minor release would cause problems.
    In 9.0, create a near-duplicate function instead.
    9d522cb3
    History
    Name Last commit Last update
    ..