1. 29 Aug, 2004 1 commit
  2. 01 Jun, 2004 1 commit
    • Tom Lane's avatar
      Align GRANT/REVOKE behavior more closely with the SQL spec, per discussion · 4b2dafcc
      Tom Lane authored
      of bug report #1150.  Also, arrange that the object owner's irrevocable
      grant-option permissions are handled implicitly by the system rather than
      being listed in the ACL as self-granted rights (which was wrong anyway).
      I did not take the further step of showing these permissions in an
      explicit 'granted by _SYSTEM' ACL entry, as that seemed more likely to
      bollix up existing clients than to do anything really useful.  It's still
      a possible future direction, though.
      4b2dafcc
  3. 02 May, 2004 1 commit
    • Bruce Momjian's avatar
      Revert patch --- needs more generalized solution. · a9d3c2cb
      Bruce Momjian authored
      > Please find a attached a small patch that adds accessor functions
      > for "aclitem" so that it is not an opaque datatype.
      >
      > I needed these functions to browse aclitems from user land. I can load
      > them when necessary, but it seems to me that these accessors for a
      > backend type belong to the backend, so I submit them.
      >
      > Fabien Coelho
      a9d3c2cb
  4. 26 Apr, 2004 1 commit
  5. 15 Sep, 2003 1 commit
  6. 01 Aug, 2003 1 commit
  7. 27 Jul, 2003 1 commit
  8. 21 Jul, 2003 1 commit
  9. 18 Jul, 2003 1 commit
  10. 04 Jul, 2003 1 commit
  11. 14 May, 2003 1 commit
  12. 23 Jan, 2003 1 commit
  13. 19 Oct, 2002 1 commit
  14. 24 Sep, 2002 1 commit
  15. 22 Sep, 2002 1 commit
    • Tom Lane's avatar
      Move most of the error checking for foreign-key constraints out of · ac355d55
      Tom Lane authored
      parse analysis and into the execution code (in tablecmds.c).  This
      eliminates a lot of unreasonably complex code that needed to have two
      or more execution paths in case it was dealing with a not-yet-created
      table column vs. an already-existing one.  The execution code is always
      dealing with already-created tables and so needs only one case.  This
      also eliminates some potential race conditions (the table wasn't locked
      between parse analysis and execution), makes it easy to fix the gripe
      about wrong referenced-column names generating a misleading error message,
      and lets us easily add a dependency from the foreign-key constraint to
      the unique index that it requires the referenced table to have.  (Cf.
      complaint from Kris Jurka 12-Sep-2002 on pgsql-bugs.)
      
      Also, third try at building a deletion mechanism that is not sensitive
      to the order in which pg_depend entries are visited.  Adding the above-
      mentioned dependency exposed the folly of what dependency.c had been
      doing: it failed for cases where B depends on C while both auto-depend
      on A.  Dropping A should succeed in this case, but was failing if C
      happened to be visited before B.  It appears the only solution is two
      separate walks over the dependency tree.
      ac355d55
  16. 16 Jul, 2002 1 commit
    • Tom Lane's avatar
      Add code to extract dependencies from an expression tree, and use it · 30ec3160
      Tom Lane authored
      to build dependencies for rules, constraint expressions, and default
      expressions.  Repair some problems in the original design of
      recursiveDeletion() exposed by more complex dependency sets.  Fix
      regression tests that were deleting things in illegal sequences.
      30ec3160
  17. 19 May, 2002 1 commit
  18. 18 May, 2002 1 commit
  19. 17 May, 2002 1 commit
  20. 27 Apr, 2002 1 commit
  21. 26 Apr, 2002 1 commit
  22. 09 Apr, 2002 1 commit
  23. 21 Mar, 2002 1 commit
  24. 06 Mar, 2002 1 commit
    • Bruce Momjian's avatar
      Change made to elog: · 92288a1c
      Bruce Momjian authored
      o  Change all current CVS messages of NOTICE to WARNING.  We were going
      to do this just before 7.3 beta but it has to be done now, as you will
      see below.
      
      o Change current INFO messages that should be controlled by
      client_min_messages to NOTICE.
      
      o Force remaining INFO messages, like from EXPLAIN, VACUUM VERBOSE, etc.
      to always go to the client.
      
      o Remove INFO from the client_min_messages options and add NOTICE.
      
      Seems we do need three non-ERROR elog levels to handle the various
      behaviors we need for these messages.
      
      Regression passed.
      92288a1c
  25. 18 Feb, 2002 1 commit
  26. 14 Jun, 2001 1 commit
  27. 09 Jun, 2001 1 commit
  28. 27 May, 2001 1 commit