1. 27 Feb, 2009 1 commit
  2. 20 Jan, 2009 1 commit
    • Peter Eisentraut's avatar
      Revise the permission checking on user mapping DDL commands. · 93a6be63
      Peter Eisentraut authored
      CREATE/ALTER/DROP USER MAPPING are now allowed either by the server owner or
      by a user with USAGE privileges for his own user name.  This is more or less
      what the SQL standard wants anyway (plus "implementation-defined")
      
      Hide information_schema.user_mapping_options.option_value, unless the current
      user is the one associated with the user mapping, or is the server owner and
      the mapping is for PUBLIC, or is a superuser.  This is to protect passwords.
      
      Also, fix a bug in information_schema._pg_foreign_servers, which hid servers
      using wrappers where the current user did not have privileges on the wrapper.
      The correct behavior is to hide servers where the current user has no
      privileges on the server.
      93a6be63
  3. 17 Jan, 2009 1 commit
  4. 19 Dec, 2008 1 commit
    • Peter Eisentraut's avatar
      SQL/MED catalog manipulation facilities · cae565e5
      Peter Eisentraut authored
      This doesn't do any remote or external things yet, but it gives modules
      like plproxy and dblink a standardized and future-proof system for
      managing their connection information.
      
      Martin Pihlak and Peter Eisentraut
      cae565e5