1. 22 Mar, 2009 1 commit
    • Tom Lane's avatar
      Remove the -d and -D options of pg_dump and pg_dumpall. The functionality · 5698f6b9
      Tom Lane authored
      is still available, but you must now write the long equivalent --inserts
      or --column-inserts.  This change is made to eliminate confusion with the
      use of -d to specify a database name in most other Postgres client programs.
      Original patch by Greg Mullane, modified per subsequent discussion.
      5698f6b9
  2. 04 Mar, 2009 1 commit
  3. 26 Feb, 2009 1 commit
  4. 17 Feb, 2009 1 commit
  5. 07 Feb, 2009 1 commit
  6. 05 Jan, 2009 1 commit
    • Tom Lane's avatar
      Add a --role option to pg_dump, pg_dumpall, and pg_restore. This allows · b0a6ad70
      Tom Lane authored
      performing dumps and restores in accordance with a security policy that
      forbids logging in directly as superuser, but instead specifies that you
      should log into an admin account and then SET ROLE to the superuser.
      
      In passing, clean up some ugly and mostly-broken code for quoting shell
      arguments in pg_dumpall.
      
      Benedek László, with some help from Tom Lane
      b0a6ad70
  7. 29 Aug, 2008 1 commit
  8. 13 Apr, 2008 1 commit
    • Tom Lane's avatar
      Turn the -i/--ignore-version options of pg_dump and pg_dumpall into no-ops: · c22ed3d5
      Tom Lane authored
      the server version check is now always enforced.  Relax the version check to
      allow a server that is of pg_dump's own major version but a later minor
      version; this is the only case that -i was at all safe to use in.
      
      pg_restore already enforced only a very weak version check, so this is
      really just a documentation change for it.
      
      Per discussion.
      c22ed3d5
  9. 26 Mar, 2008 1 commit
  10. 20 Mar, 2008 1 commit
  11. 11 Dec, 2007 1 commit
  12. 26 Mar, 2007 1 commit
  13. 21 Feb, 2007 1 commit
  14. 20 Feb, 2007 1 commit
  15. 01 Feb, 2007 1 commit
  16. 31 Jan, 2007 1 commit
    • Bruce Momjian's avatar
      Update reference documentation on may/can/might: · e81c138e
      Bruce Momjian authored
      Standard English uses "may", "can", and "might" in different ways:
      
              may - permission, "You may borrow my rake."
      
              can - ability, "I can lift that log."
      
              might - possibility, "It might rain today."
      
      Unfortunately, in conversational English, their use is often mixed, as
      in, "You may use this variable to do X", when in fact, "can" is a better
      choice.  Similarly, "It may crash" is better stated, "It might crash".
      e81c138e
  17. 25 Jan, 2007 4 commits
  18. 15 Jan, 2007 1 commit
  19. 07 Oct, 2006 1 commit
    • Peter Eisentraut's avatar
      The -X option in pg_dump was supposed to be a workaround for the lack of · 2b25e116
      Peter Eisentraut authored
      portable long options.  But we have had portable long options for a long
      time now, so this is obsolete.  Now people have added options which *only*
      work with -X but not as regular long option, so I'm putting a stop to this:
      -X is deprecated; it still works, but it has been removed from the
      documentation, and please don't add more of them.
      2b25e116
  20. 16 Sep, 2006 1 commit
  21. 16 Jun, 2006 1 commit
  22. 01 Nov, 2005 1 commit
  23. 15 Oct, 2005 1 commit
  24. 10 Oct, 2005 1 commit
    • Tom Lane's avatar
      Remove the DELETEs from pg_shadow and pg_group that pg_dumpall used to · c6b9924b
      Tom Lane authored
      emit when given the --clean option, in favor of individual DROP ROLE
      commands.  The old technique could not possibly work in 8.1, and was
      never a very good idea anyway IMHO.  The DROP ROLE approach has the
      defect that the DROPs will fail for roles that own objects or have
      privileges, but perhaps we can improve that later.
      c6b9924b
  25. 25 Jul, 2005 1 commit
  26. 21 Jun, 2005 2 commits
    • Tom Lane's avatar
      pg_dump can now dump large objects even in plain-text output mode, by · 7a28de20
      Tom Lane authored
      using the recently added lo_create() function.  The restore logic in
      pg_restore is greatly simplified as well, since there's no need anymore
      to try to adjust database references to match a new set of blob OIDs.
      7a28de20
    • Tom Lane's avatar
      Cause initdb to create a third standard database "postgres", which · 6f7fc0ba
      Tom Lane authored
      unlike template0 and template1 does not have any special status in
      terms of backend functionality.  However, all external utilities such
      as createuser and createdb now connect to "postgres" instead of
      template1, and the documentation is changed to encourage people to use
      "postgres" instead of template1 as a play area.  This should fix some
      longstanding gotchas involving unexpected propagation of database
      objects by createdb (when you used template1 without understanding
      the implications), as well as ameliorating the problem that CREATE
      DATABASE is unhappy if anyone else is connected to template1.
      Patch by Dave Page, minor editing by Tom Lane.  All per recent
      pghackers discussions.
      6f7fc0ba
  27. 29 May, 2005 1 commit
  28. 06 Jan, 2005 1 commit
  29. 04 Jan, 2005 1 commit
  30. 19 Jul, 2004 1 commit
    • Bruce Momjian's avatar
      Here is another patch that fixes a stack of pg_dump bugs: · 45995219
      Bruce Momjian authored
      * Fix help text ordering
      
      * Add back --set-session-authorization to pg_dumpall.  Updated the docs
      for that.  Updated help for that.
      
      * Dump ALTER USER commands for the cluster owner ("pgsql").  These are
      dumped AFTER the create user and create database commands in case the
      permissions to do these have been revoked.
      
      * Dump ALTER OWNER for public schema (because it's possible to change
      it).  This was done by adding TOC entries for the public schema, and
      filtering them out at archiver time.  I also save the owner in the TOC
      entry just for the public schema.
      
      * Suppress dumping single quotes around schema_path and DateStyle
      options when they are set using ALTER USER or ALTER DATABASE.  Added a
      comment to the steps in guc.c to remind people to update that list.
      
      * Fix dumping in --clean mode against a pre-7.3 server.  It just sets
      all drop statements to assume the public schema, allowing it to restore
      without error.
      
      * Cleaned up text output.  eg. Don't output -- Tablespaces comment if
      there are none.  Same for groups and users.
      
      * Make the commands to DELETE FROM pg_shadow and DELETE FROM pg_group
      only be output when -c mode is enabled.  I'm not sure why that hasn't
      been done before?!?!
      
      This should be good for application asap, after which I will start on
      regression dumping 7.0-7.4 databases.
      
      Christopher Kings-Lynne
      45995219
  31. 12 Jul, 2004 1 commit
  32. 07 Jun, 2004 1 commit
  33. 29 Nov, 2003 1 commit
    • PostgreSQL Daemon's avatar
      · 969685ad
      PostgreSQL Daemon authored
      $Header: -> $PostgreSQL Changes ...
      969685ad
  34. 04 Nov, 2003 1 commit
  35. 02 Nov, 2003 1 commit
  36. 31 Aug, 2003 1 commit