1. 07 Apr, 1999 1 commit
    • Tom Lane's avatar
      Fix some more hashjoin-related bugs in pg_operator. Fix · af871480
      Tom Lane authored
      hashjoin's hashFunc() so that it does the right thing with pass-by-value
      data types (the old code would always return 0 for int2 or char values,
      which would work but would slow things down a lot).  Extend opr_sanity
      regress test to catch more kinds of errors.
      af871480
  2. 13 Feb, 1999 1 commit
  3. 03 Feb, 1999 1 commit
  4. 17 Jan, 1999 1 commit
  5. 15 Dec, 1998 1 commit
  6. 14 Dec, 1998 3 commits
    • Marc G. Fournier's avatar
      · 9396802f
      Marc G. Fournier authored
      more cleanups...of note, appendStringInfo now performs like sprintf(),
      where you state a format and arguments.  the old behavior required
      each appendStringInfo to have to have a sprintf() before it if any
      formatting was required.
      
      Also shortened several instances where there were multiple appendStringInfo()
      calls in a row, doing nothing more then adding one more word to the String,
      instead of doing them all in one call.
      9396802f
    • Marc G. Fournier's avatar
      · df1468e2
      Marc G. Fournier authored
      Many more cleanups...
      df1468e2
    • Marc G. Fournier's avatar
      · 7c3b7d27
      Marc G. Fournier authored
      Initial attempt to clean up the code...
      
      Switch sprintf() to snprintf()
      Remove any/all #if 0 -or- #ifdef NOT_USED -or- #ifdef FALSE sections of
      	code
      7c3b7d27
  7. 27 Nov, 1998 1 commit
  8. 01 Sep, 1998 2 commits
  9. 15 Jun, 1998 1 commit
  10. 26 Feb, 1998 1 commit
  11. 13 Feb, 1998 1 commit
    • Vadim B. Mikheev's avatar
      Support for subselects. · 1a105cef
      Vadim B. Mikheev authored
      ExecReScan for nodeAgg, nodeHash, nodeHashjoin, nodeNestloop and nodeResult.
      Fixed ExecReScan for nodeMaterial.
      Get rid of #ifdef INDEXSCAN_PATCH.
      Get rid of ExecMarkPos and ExecRestrPos in nodeNestloop.
      1a105cef
  12. 11 Feb, 1998 1 commit
  13. 25 Jan, 1998 1 commit
  14. 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
  15. 07 Jan, 1998 1 commit
  16. 05 Jan, 1998 1 commit
  17. 08 Sep, 1997 2 commits
  18. 07 Sep, 1997 1 commit
  19. 19 Aug, 1997 1 commit
  20. 28 Jul, 1997 1 commit
  21. 22 Apr, 1997 1 commit
  22. 06 Nov, 1996 1 commit
  23. 31 Oct, 1996 1 commit
  24. 26 Oct, 1996 1 commit
  25. 19 Aug, 1996 1 commit
    • Marc G. Fournier's avatar
      |From: Dan McGuirk <mcguirk@indirect.com> · f796387b
      Marc G. Fournier authored
      |
      |This patch fixes a backend crash that happens sometimes when you try to
      |join on a field that contains NULL in some rows.  Postgres tries to
      |compute a hash value of the field you're joining on, but when the field
      |is NULL, the pointer it thinks is pointing to the data is really just
      |pointing to random memory.  This forces the hash value of NULL to be 0.
      |
      |It seems that nothing matches NULL on joins, even other NULL's (with or
      |without this patch).  Is that what's supposed to happen?
      |
      f796387b
  26. 26 Jul, 1996 1 commit
  27. 22 Jul, 1996 1 commit
    • Marc G. Fournier's avatar
      More of Dr. George's changes... · e11744e1
      Marc G. Fournier authored
              - src/backend/catalog/*
                      - no changes
              - src/backend/executor/*
                      - change how nodeHash.c handles running out of memory
              - src/backend/optimizer/*
                      - mostly cosmetic changes
      e11744e1
  28. 09 Jul, 1996 1 commit