1. 31 Jan, 1998 1 commit
  2. 25 Jan, 1998 2 commits
  3. 15 Jan, 1998 1 commit
    • PostgreSQL Daemon's avatar
      Thank god for searchable mail archives. · baef78d9
      PostgreSQL Daemon authored
      Patch by: wieck@sapserv.debis.de (Jan Wieck)
      
         One  of  the design rules of PostgreSQL is extensibility. And
         to follow this rule means (at least for me) that there should
         not  only  be a builtin PL.  Instead I would prefer a defined
         interface for PL implemetations.
      baef78d9
  4. 13 Jan, 1998 1 commit
    • Marc G. Fournier's avatar
      Some *very* major changes by darrenk@insightdist.com (Darren King) · 374bb5d2
      Marc G. Fournier authored
      ==========================================
      What follows is a set of diffs that cleans up the usage of BLCKSZ.
      
      As a side effect, the person compiling the code can change the
      value of BLCKSZ _at_their_own_risk_.  By that, I mean that I've
      tried it here at 4096 and 16384 with no ill-effects.  A value
      of 4096 _shouldn't_ affect much as far as the kernel/file system
      goes, but making it bigger than 8192 can have severe consequences
      if you don't know what you're doing.  16394 worked for me, _BUT_
      when I went to 32768 and did an initdb, the SCSI driver broke and
      the partition that I was running under went to hell in a hand
      basket. Had to reboot and do a good bit of fsck'ing to fix things up.
      
      The patch can be safely applied though.  Just leave BLCKSZ = 8192
      and everything is as before.  It basically only cleans up all of the
      references to BLCKSZ in the code.
      
      If this patch is applied, a comment in the config.h file though above
      the BLCKSZ define with warning about monkeying around with it would
      be a good idea.
      
      Darren  darrenk@insightdist.com
      
      (Also cleans up some of the #includes in files referencing BLCKSZ.)
      ==========================================
      374bb5d2
  5. 07 Jan, 1998 1 commit
  6. 05 Jan, 1998 1 commit
  7. 24 Nov, 1997 1 commit
  8. 25 Oct, 1997 1 commit
  9. 15 Oct, 1997 1 commit
  10. 26 Sep, 1997 1 commit
  11. 18 Sep, 1997 2 commits
    • Vadim B. Mikheev's avatar
      Don't limit number of tuples in leftist trees! · b0ccd784
      Vadim B. Mikheev authored
      Use qsort to sort array of tuples for nextrun when current
      run is done and put into leftist tree from sorted array!
      It's much faster and creates non-bushy tree - this is ve-e-ery good
      for perfomance!
      b0ccd784
    • Vadim B. Mikheev's avatar
      1. Use qsort for first run · 712ea250
      Vadim B. Mikheev authored
      2. Limit number of tuples in leftist trees:
      	- put one tuple from current tree to disk if limit reached;
      	- end run creation if limit reached by nextrun.
      3. Avoid mergeruns() if first run is single one!
      712ea250
  12. 15 Sep, 1997 1 commit
  13. 08 Sep, 1997 2 commits
  14. 07 Sep, 1997 1 commit
  15. 05 Sep, 1997 1 commit
  16. 19 Aug, 1997 1 commit
  17. 18 Aug, 1997 1 commit
  18. 14 Aug, 1997 2 commits
  19. 12 Aug, 1997 2 commits
  20. 06 Aug, 1997 6 commits
  21. 24 Jul, 1997 1 commit
  22. 20 May, 1997 1 commit
  23. 06 Nov, 1996 1 commit
  24. 03 Nov, 1996 1 commit
  25. 09 Jul, 1996 1 commit