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
    Noah Misch authored
    These programs nominally accepted conninfo strings, but they would
    proceed to use the original dbname parameter as though it were an
    unadorned database name.  This caused "reindexdb dbname=foo" to issue an
    SQL command that always failed, and other programs printed a conninfo
    string in error messages that purported to print a database name.  Fix
    both problems by using PQdb() to retrieve actual database names.
    Continue to print the full conninfo string when reporting a connection
    failure.  It is informative there, and if the database name is the sole
    problem, the server-side error message will include the name.  Beyond
    those user-visible fixes, this allows a subsequent commit to synthesize
    and use conninfo strings without that implementation detail leaking into
    messages.  As a side effect, the "vacuuming database" message now
    appears after, not before, the connection attempt.  Back-patch to 9.1
    (all supported versions).
    
    Reviewed by Michael Paquier and Peter Eisentraut.
    
    Security: CVE-2016-5424
    05abd3bc
    History
    Name Last commit Last update