1. 29 Apr, 2008 1 commit
  2. 26 Mar, 2008 1 commit
  3. 24 Mar, 2008 2 commits
  4. 23 Jan, 2008 1 commit
  5. 01 Jan, 2008 1 commit
  6. 15 Nov, 2007 1 commit
  7. 14 May, 2007 2 commits
  8. 11 May, 2007 1 commit
    • Tom Lane's avatar
      Support arrays of composite types, including the rowtypes of regular tables · bc8036fc
      Tom Lane authored
      and views (but not system catalogs, nor sequences or toast tables).  Get rid
      of the hardwired convention that a type's array type is named exactly "_type",
      instead using a new column pg_type.typarray to provide the linkage.  (It still
      will be named "_type", though, except in odd corner cases such as
      maximum-length type names.)
      
      Along the way, make tracking of owner and schema dependencies for types more
      uniform: a type directly created by the user has these dependencies, while a
      table rowtype or auto-generated array type does not have them, but depends on
      its parent object instead.
      
      David Fetter, Andrew Dunstan, Tom Lane
      bc8036fc
  9. 03 Mar, 2007 1 commit
  10. 05 Jan, 2007 1 commit
  11. 04 Oct, 2006 1 commit
  12. 21 Aug, 2006 1 commit
    • Tom Lane's avatar
      Fix all known problems with pg_dump's handling of serial sequences · 2b2a5072
      Tom Lane authored
      by abandoning the idea that it should say SERIAL in the dump.  Instead,
      dump serial sequences and column defaults just like regular ones.
      Add a new backend command ALTER SEQUENCE OWNED BY to let pg_dump recreate
      the sequence-to-column dependency that was formerly created "behind the
      scenes" by SERIAL.  This restores SERIAL to being truly "just a macro"
      consisting of component operations that can be stated explicitly in SQL.
      Furthermore, the new command allows sequence ownership to be reassigned,
      so that old mistakes can be cleaned up.
      
      Also, downgrade the OWNED-BY dependency from INTERNAL to AUTO, since there
      is no longer any very compelling argument why the sequence couldn't be
      dropped while keeping the column.  (This forces initdb, to be sure the
      right kinds of dependencies are in there.)
      
      Along the way, add checks to prevent ALTER OWNER or SET SCHEMA on an
      owned sequence; you can now only do this indirectly by changing the
      owning table's owner or schema.  This is an oversight in previous
      releases, but probably not worth back-patching.
      2b2a5072
  13. 20 Aug, 2006 1 commit
    • Alvaro Herrera's avatar
      Fix DROP OWNED BY to correctly consider the implicitly-deleted objects list for · df18c51f
      Alvaro Herrera authored
      each object to be deleted, instead of the previous hack that just skipped
      INTERNAL dependencies, which didn't really work.  Per report from Tom Lane.
      
      To do this, introduce a new performMultipleDeletions entry point in
      dependency.c to delete multiple objects at once.  The dependency code then has
      the responsability of tracking INTERNAL and AUTO dependencies as needed.
      
      Along the way, change ObjectAddresses so that we can allocate an ObjectAddress
      list from outside dependency.c and not have to export the internal
      representation.
      df18c51f
  14. 14 Jul, 2006 1 commit
  15. 13 Jul, 2006 1 commit
  16. 11 Jul, 2006 1 commit
  17. 04 May, 2006 1 commit
    • Tom Lane's avatar
      Rethink the locking mechanisms used for CREATE/DROP/RENAME DATABASE. · 52667d56
      Tom Lane authored
      The former approach used ExclusiveLock on pg_database, which being a
      cluster-wide lock meant only one of these operations could proceed at
      a time; worse, it also blocked all incoming connections in ReverifyMyDatabase.
      Now that we have LockSharedObject(), we can use locks of different types
      applied to databases considered as objects.  This allows much more
      flexible management of the interlocking: two CREATE DATABASEs need not
      block each other, and need not block connections except to the template
      database being used.  Similarly DROP DATABASE doesn't block unrelated
      operations.  The locking used in flatfiles.c is also much narrower in
      scope than before.  Per recent proposal.
      52667d56
  18. 05 Mar, 2006 1 commit
  19. 21 Jan, 2006 1 commit
    • Bruce Momjian's avatar
      Add GRANT ON SEQUENCE syntax to support sequence-only permissions. · 4789e988
      Bruce Momjian authored
      Continue to support GRANT ON [TABLE] for sequences for backward
      compatibility;  issue warning for invalid sequence permissions.
      
      [Backward compatibility warning message.]
      
      Add USAGE permission for sequences that allows only currval() and
      nextval(), not setval().
      
      Mention object name in grant/revoke warnings because of possible
      multi-object operations.
      4789e988
  20. 01 Dec, 2005 1 commit
  21. 22 Nov, 2005 1 commit
  22. 21 Nov, 2005 1 commit
    • Alvaro Herrera's avatar
      Implement DROP OWNED and REASSIGN OWNED. These new commands facilitate the · cec3b0a9
      Alvaro Herrera authored
      process of dropping roles by dropping objects owned by them and privileges
      granted to them, or giving the owned objects to someone else, through the
      use of the data stored in the new pg_shdepend catalog.
      
      Some refactoring of the GRANT/REVOKE code was needed, as well as ALTER OWNER
      code.  Further cleanup of code duplication in the GRANT code seems necessary.
      
      Implemented by me after an idea from Tom Lane, who also provided various kind
      of implementation advice.
      
      Regression tests pass.  Some tests for the new functionality are also added,
      as well as rudimentary documentation.
      cec3b0a9
  23. 15 Oct, 2005 1 commit
  24. 30 Aug, 2005 1 commit
  25. 07 Jul, 2005 1 commit