1. 09 Jun, 2000 1 commit
  2. 02 Jun, 2000 1 commit
  3. 12 Apr, 2000 1 commit
  4. 26 Jan, 2000 1 commit
    • Bruce Momjian's avatar
      Add: · 5c25d602
      Bruce Momjian authored
        * Portions Copyright (c) 1996-2000, PostgreSQL, Inc
      
      to all files copyright Regents of Berkeley.  Man, that's a lot of files.
      5c25d602
  5. 10 Dec, 1999 1 commit
  6. 17 Jul, 1999 1 commit
  7. 16 Jul, 1999 2 commits
  8. 15 Jul, 1999 3 commits
  9. 04 Jun, 1999 1 commit
  10. 31 May, 1999 1 commit
  11. 25 May, 1999 1 commit
  12. 10 May, 1999 1 commit
  13. 09 May, 1999 2 commits
  14. 03 May, 1999 1 commit
    • Bruce Momjian's avatar
      here are some patches for 6.5.0 which I already submitted but have never · 210055ad
      Bruce Momjian authored
      been applied. The patches are in the .tar.gz attachment at the end:
      
      varchar-array.patch     this patch adds support for arrays of bpchar() and
                              varchar(), which where always missing from postgres.
      
                              These datatypes can be used to replace the _char4,
                              _char8, etc., which were dropped some time ago.
      
      block-size.patch        this patch fixes many errors in the parser and other
                              program which happen with very large query statements
                              (> 8K) when using a page size larger than 8192.
      
                              This patch is needed if you want to submit queries
                              larger than 8K. Postgres supports tuples up to 32K
                              but you can't insert them because you can't submit
                              queries larger than 8K. My patch fixes this problem.
      
                              The patch also replaces all the occurrences of `8192'
                              and `1<<13' in the sources with the proper constants
                              defined in include files. You should now never find
                              8192 hardwired in C code, just to make code clearer.
      
      
      --
      Massimo Dal Zotto
      210055ad
  15. 13 Feb, 1999 1 commit
  16. 17 Jan, 1999 1 commit
  17. 01 Sep, 1998 2 commits
  18. 19 Aug, 1998 1 commit
    • Bruce Momjian's avatar
      heap_fetch requires buffer pointer, must be released; heap_getnext · 79715390
      Bruce Momjian authored
      no longer returns buffer pointer, can be gotten from scan;
      	descriptor; bootstrap can create multi-key indexes;
      pg_procname index now is multi-key index; oidint2, oidint4, oidname
      are gone (must be removed from regression tests); use System Cache
      rather than sequential scan in many places; heap_modifytuple no
      longer takes buffer parameter; remove unused buffer parameter in
      a few other functions; oid8 is not index-able; remove some use of
      single-character variable names; cleanup Buffer variables usage
      and scan descriptor looping; cleaned up allocation and freeing of
      tuples; 18k lines of diff;
      79715390
  19. 22 Jul, 1998 1 commit
  20. 21 Jul, 1998 1 commit
    • Bruce Momjian's avatar
      Theses buffer leaks are caused by indexes that are kept open between · e0058b61
      Bruce Momjian authored
      calls. Outside a transaction, the backend detects them as buffer
      leaks; it sends a NOTICE, and frees them. This sometimes cause a
      segmentation fault (at least on Linux). These indexes are initialized
      on the first lo_read/lo_write/lo_tell call, and (normally) closed
      on a lo_close call.  Thus the buffer leaks appear when lo direct
      access functions are used, and not with lo_import/lo_export functions
      (libpq version calls lo_close before ending the command, and the
      backend version uses another path).
      
      The included patches (against recent snapshot, and against 6.3.2)
      cause indexes to be closed on transaction end (that is on explicit
      'END' statment, or on command termination outside trasaction blocks),
      thus preventing the buffer leaks while increasing performance inside
      transactions. Some (all?) 'classic' memory leaks are also removed.
      
      I hope it will be ok.
      
      --- Pascal ANDRE, graduated from Ecole Centrale Paris andre@via.ecp.fr
      e0058b61
  21. 15 Jun, 1998 1 commit
  22. 12 May, 1998 1 commit
  23. 07 Jan, 1998 1 commit
  24. 05 Jan, 1998 1 commit
  25. 08 Dec, 1997 1 commit
  26. 25 Oct, 1997 1 commit
  27. 08 Sep, 1997 2 commits
  28. 07 Sep, 1997 1 commit
  29. 12 Aug, 1997 2 commits
  30. 10 Jun, 1997 1 commit
  31. 06 May, 1997 1 commit
  32. 21 Apr, 1997 1 commit
  33. 17 Apr, 1997 1 commit
    • Marc G. Fournier's avatar
      From: Raymond Toy <toy@rtp.ericsson.se> · cbaa9883
      Marc G. Fournier authored
      Subject: [PATCHES] 970417:  some large object patches
      
      
      Two patches here, made against 970417.  Both have to do with large
      objects:
      
              1.  lobjfuncs was not initialized in PQconnectdb.  This causes
                  failure later if large objects are used.  (Someone already
                  caught this error in PQsetdb.)
      
              2.  Postgres functions lo_import and lo_export sometimes
                  produce garbage for the file names because the filename
                  strings aren't always terminated by \0.  (VARDATA isn't
                  necessarily null terminated.)
      cbaa9883