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
    settings: avoid calling superuser() in contexts where it's not defined,
    don't leak the transient copies of GetConfigOption output, and avoid the
    whole exercise in postmaster child processes.
    
    I found that actually no current caller of GetConfigOption has any use for
    its internal check of GUC_SUPERUSER_ONLY.  But rather than just remove
    that entirely, it seemed better to add a parameter indicating whether to
    enforce the check.
    
    Per report from Simon and subsequent testing.
    54d60bbd
    History
    Name Last commit Last update