1. 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
  2. 11 Jan, 2006 1 commit
  3. 03 Dec, 2005 1 commit
    • Tom Lane's avatar
      Treat procedural languages as owned by the bootstrap superuser, rather · e4a9229d
      Tom Lane authored
      than owned by nobody.  This results in cleaner display of language ACLs,
      since the backend's aclchk.c uses the same convention.  AFAICS there is
      no practical difference but it's nice to avoid emitting SET SESSION
      AUTHORIZATION; also this will make it easier to transition pg_dump to
      some future version in which we may include an explicit ownership column
      in pg_language.  Per gripe from David Begley.
      e4a9229d
  4. 02 Dec, 2005 1 commit
  5. 22 Nov, 2005 1 commit
  6. 15 Oct, 2005 1 commit
  7. 02 Jul, 2005 1 commit
  8. 01 Jul, 2005 1 commit
  9. 30 Apr, 2005 1 commit
    • Neil Conway's avatar
      GCC 4.0 includes a new warning option, -Wformat-literal, that emits · 47458f8c
      Neil Conway authored
      a warning when a variable is used as a format string for printf()
      and similar functions (if the variable is derived from untrusted
      data, it could include unexpected formatting sequences). This
      emits too many warnings to be enabled by default, but it does
      flag a few dubious constructs in the Postgres tree. This patch
      fixes up the obvious variants: functions that are passed a variable
      format string but no additional arguments.
      
      Most of these are harmless (e.g. the ruleutils stuff), but there
      is at least one actual bug here: if you create a trigger named
      "%sfoo", pg_dump will read uninitialized memory and fail to dump
      the trigger correctly.
      47458f8c
  10. 31 Dec, 2004 1 commit
    • PostgreSQL Daemon's avatar
      · 2ff50159
      PostgreSQL Daemon authored
      Tag appropriate files for rc3
      
      Also performed an initial run through of upgrading our Copyright date to
      extend to 2005 ... first run here was very simple ... change everything
      where: grep 1996-2004 && the word 'Copyright' ... scanned through the
      generated list with 'less' first, and after, to make sure that I only
      picked up the right entries ...
      2ff50159
  11. 29 Aug, 2004 2 commits
  12. 18 Jun, 2004 1 commit
  13. 23 Mar, 2004 1 commit
  14. 07 Jan, 2004 1 commit
  15. 29 Nov, 2003 1 commit
    • PostgreSQL Daemon's avatar
      · 969685ad
      PostgreSQL Daemon authored
      $Header: -> $PostgreSQL Changes ...
      969685ad
  16. 14 Aug, 2003 1 commit
  17. 04 Aug, 2003 2 commits
  18. 31 Jul, 2003 1 commit
  19. 24 Jul, 2003 1 commit
  20. 30 May, 2003 1 commit
  21. 07 Sep, 2002 1 commit
  22. 04 Sep, 2002 1 commit
  23. 27 Aug, 2002 1 commit