1. 01 Oct, 2008 3 commits
  2. 30 Sep, 2008 5 commits
  3. 28 Sep, 2008 2 commits
  4. 27 Sep, 2008 1 commit
  5. 26 Sep, 2008 2 commits
  6. 25 Sep, 2008 1 commit
  7. 24 Sep, 2008 8 commits
  8. 23 Sep, 2008 5 commits
  9. 22 Sep, 2008 2 commits
    • Tom Lane's avatar
      Get rid of pgpass_from_client tracking inside libpq --- given the conclusion · c52aab55
      Tom Lane authored
      that presence of the password in the conninfo string must be checked *before*
      risking a connection attempt, there is no point in checking it afterwards.
      This makes the specification of PQconnectionUsedPassword() a bit simpler
      and perhaps more generally useful, too.
      c52aab55
    • Tom Lane's avatar
      Fix dblink_connect() so that it verifies that a password is supplied in the · cae7ad90
      Tom Lane authored
      conninfo string *before* trying to connect to the remote server, not after.
      As pointed out by Marko Kreen, in certain not-very-plausible situations
      this could result in sending a password from the postgres user's .pgpass file,
      or other places that non-superusers shouldn't have access to, to an
      untrustworthy remote server.  The cleanest fix seems to be to expose libpq's
      conninfo-string-parsing code so that dblink can check for a password option
      without duplicating the parsing logic.
      
      Joe Conway, with a little cleanup by Tom Lane
      cae7ad90
  10. 21 Sep, 2008 1 commit
  11. 19 Sep, 2008 6 commits
  12. 17 Sep, 2008 4 commits