1. 23 Jul, 1997 1 commit
  2. 20 Jun, 1997 1 commit
  3. 07 Jun, 1997 2 commits
  4. 05 Jun, 1997 1 commit
  5. 02 Jun, 1997 1 commit
    • Marc G. Fournier's avatar
      From: Igor <igor@sba.miami.edu> · f9f98e3a
      Marc G. Fournier authored
      Subject: [PATCHES] pg_dump memory leak patch
      
      This patch fixes a HUGE memory leak problem in pg_dump.
      Pretty much anything that was allocated was never freed and Purify
      reported about 40% possible memory leak and 6% actual leak. I added
      functions to clear out all the allocated structures. After the patch
      Purify returns 0 for number of bytes leaked...
      f9f98e3a
  6. 06 May, 1997 1 commit
  7. 12 Apr, 1997 1 commit
  8. 02 Apr, 1997 1 commit
  9. 01 Mar, 1997 1 commit
  10. 13 Feb, 1997 1 commit
  11. 09 Feb, 1997 1 commit
  12. 07 Jan, 1997 1 commit
  13. 30 Dec, 1996 1 commit
  14. 28 Dec, 1996 1 commit
  15. 27 Dec, 1996 1 commit
  16. 26 Nov, 1996 2 commits
  17. 20 Nov, 1996 1 commit
  18. 17 Nov, 1996 1 commit
  19. 10 Nov, 1996 1 commit
  20. 08 Nov, 1996 1 commit
  21. 04 Nov, 1996 1 commit
  22. 07 Oct, 1996 2 commits
  23. 02 Oct, 1996 1 commit
  24. 16 Sep, 1996 1 commit
  25. 24 Aug, 1996 1 commit
    • Marc G. Fournier's avatar
      The patch does several things: · 208a30f2
      Marc G. Fournier authored
              It adds a WITH OIDS option to the copy command, which allows
      dumping and loading of oids.
      
              If a copy command tried to load in an oid that is greater than
      its current system max oid, the system max oid is incremented.  No
      checking is done to see if other backends are running and have cached
      oids.
      
              pg_dump as its first step when using the -o (oid) option, will
      copy in a dummy row to set the system max oid value so as rows are
      loaded in, they are certain to be lower than the system oid.
      
              pg_dump now creates indexes at the end to speed loading
      
      
      Submitted by:  Bruce Momjian <maillist@candle.pha.pa.us>
      208a30f2
  26. 14 Aug, 1996 1 commit
    • Marc G. Fournier's avatar
      This patch can be installed as part of 1.02.1 so people can properly · e7a110b4
      Marc G. Fournier authored
      pg_dump and load to 2.0.  I haven't gotten any feedback on whether
      people want it, so I am submitting it for others to decide.  I would
      recommend an install in 1.02.1.
      
      I had said that the 2.0 pg_dump could dump a 1.02.1 database, but I was
      wrong.  The copy is actually performed by the backend, and the 2.0
      database will not be able to read 1.02.1 databases because of the new
      system columns.
      
      This patch does several things.  It copies nulls out as \N, so they can
      be distinguished from '' strings.  It fixes a problem where backslashes
      in the input stream were not output as double-backslashes.  Without this
      patch, backslashes copied out were deleted upon input, or interpreted as
      special characters.  Third, input is now terminated by backslash-period.
      This can not be part of a normal input stream.
      
      I tested this by creating a database with all sorts of nulls, backslash,
      and period fields and dumped the database and reloaded into a new
      database and compared them.
      
      Submitted by: Bruce
      e7a110b4
  27. 31 Jul, 1996 1 commit
  28. 27 Jul, 1996 1 commit
  29. 22 Jul, 1996 1 commit
  30. 12 Jul, 1996 1 commit
  31. 09 Jul, 1996 1 commit