1. 28 May, 2002 1 commit
    • Tom Lane's avatar
      Rework pg_dump namespace search criteria so that dumping of user objects · 36a1e732
      Tom Lane authored
      having names conflicting with system objects will work --- the search
      path is now user-schema, pg_catalog rather than implicitly the other way
      around.  Note this requires being careful to explicitly qualify references
      to system names whenever pg_catalog is not first in the search path.
      Also, add support for dumping ACLs of schemas.
      36a1e732
  2. 22 May, 2002 1 commit
    • Peter Eisentraut's avatar
      Add optional "validator" function to languages that can validate the · d60f10b0
      Peter Eisentraut authored
      function body (and other properties) as a function in the language
      is created.  This generalizes ad hoc code that already existed for
      the built-in languages.
      
      The validation now happens after the pg_proc tuple of the new function
      is created, so it is possible to define recursive SQL functions.
      
      Add some regression test cases that cover bogus function definition
      attempts.
      d60f10b0
  3. 19 May, 2002 1 commit
  4. 18 May, 2002 1 commit
  5. 17 May, 2002 1 commit
  6. 13 May, 2002 1 commit
    • Tom Lane's avatar
      Make operators have their own comments separate from those of the · f69bc37b
      Tom Lane authored
      underlying function; but cause psql's \do to show the underlying
      function's comment if the operator has no comment of its own, to preserve
      the useful functionality of the original behavior.  Also, implement
      COMMENT ON SCHEMA.  Patch from Rod Taylor.
      f69bc37b
  7. 10 May, 2002 1 commit
  8. 06 May, 2002 1 commit
  9. 29 Apr, 2002 2 commits
  10. 24 Apr, 2002 4 commits
  11. 21 Apr, 2002 1 commit
  12. 19 Apr, 2002 1 commit
  13. 18 Apr, 2002 1 commit
    • Tom Lane's avatar
      Rule names are now unique per-relation, rather than unique globally. · b3120804
      Tom Lane authored
      DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause,
      similar to TRIGGER syntaxes.  To allow loading of existing pg_dump
      files containing COMMENT ON RULE, the COMMENT code will still accept
      the old syntax --- but only if the target rulename is unique across
      the whole database.
      b3120804
  14. 13 Apr, 2002 1 commit
    • Bruce Momjian's avatar
      Rod's patch does what it is supposed to do, but it also includes · 7603c42e
      Bruce Momjian authored
      some old code to add PK constraints to CREATE TABLE. That stuff
      had been removed as part of my original patch for pg_dump a
      little while ago.
      
      The attached patch fixes this by removing (again :-) ) the
      code in dumpTables() to perform PK creation during CREATE
      TABLE. I briefly tested it locally and it fixes both of
      Tom's test cases.
      
      Please apply.
      
      Cheers,
      
      Neil
      
      --
      Neil Conway <neilconway@rogers.com>
      7603c42e
  15. 11 Apr, 2002 1 commit
    • Tom Lane's avatar
      Restructure representation of aggregate functions so that they have pg_proc · 902a6a0a
      Tom Lane authored
      entries, per pghackers discussion.  This fixes aggregates to live in
      namespaces, and also simplifies/speeds up lookup in parse_func.c.
      Also, add a 'proimplicit' flag to pg_proc that controls whether a type
      coercion function may be invoked implicitly, or only explicitly.  The
      current settings of these flags are more permissive than I would like,
      but we will need to debate and refine the behavior; for now, I avoided
      breaking regression tests as much as I could.
      902a6a0a
  16. 05 Apr, 2002 2 commits
  17. 21 Mar, 2002 1 commit
  18. 06 Mar, 2002 1 commit
    • Bruce Momjian's avatar
      Enable ALTER TABLE ADD PRIMARY KEY for pg_dump, for performance reasons · 5b5cef9a
      Bruce Momjian authored
      so index is not on table during COPY.
      
      > > AFAICT, the patch I posted to -patches a little while to enable the
      > > usage of ALTER TABLE ADD PRIMARY KEY by pg_dump hasn't been applied, nor
      > > is it in the unapplied patches list. I was under the impression that
      > > this was in the queue for application -- did it just get lost?
      
      Neil Conway <neilconway@rogers.com>
      5b5cef9a
  19. 27 Feb, 2002 1 commit
  20. 11 Feb, 2002 1 commit
  21. 06 Feb, 2002 1 commit
  22. 25 Jan, 2002 1 commit
  23. 18 Jan, 2002 1 commit
  24. 11 Jan, 2002 1 commit
    • Tom Lane's avatar
      Fix pg_dump to read-lock all tables to be dumped as soon as it's read · 0e1a5075
      Tom Lane authored
      their names from pg_class.  This considerably reduces the window wherein
      someone could DROP or ALTER a table that pg_dump is intending to dump.
      Not a perfect solution, but definitely an improvement.  Per complaints
      from Marc Fournier; patch by Brent Verner with some kibitzing by Tom Lane.
      0e1a5075
  25. 28 Oct, 2001 1 commit
  26. 25 Oct, 2001 1 commit
  27. 22 Oct, 2001 1 commit
  28. 03 Oct, 2001 2 commits
  29. 01 Oct, 2001 1 commit
    • Tom Lane's avatar
      Change pg_dump to produce CREATE INDEX commands by using the backend's · 1929a90b
      Tom Lane authored
      pg_get_indexdef() function, rather than reaching into the system catalogs
      for itself.  This eliminates a fair amount of redundant code.  Also,
      since I just changed pg_get_indexdef() to suppress display of default
      index opclasses, this will mean that 7.2 and later dumps will not mention
      opclasses unless they are non-default opclasses.  Should make life easier
      for future index opclass reorganizations.
      1929a90b
  30. 21 Sep, 2001 1 commit
  31. 07 Sep, 2001 1 commit
  32. 06 Sep, 2001 1 commit
  33. 27 Aug, 2001 2 commits