1. 23 Mar, 2001 1 commit
  2. 22 Mar, 2001 1 commit
  3. 24 Jan, 2001 1 commit
  4. 25 Oct, 2000 1 commit
  5. 13 Aug, 2000 1 commit
    • Tom Lane's avatar
      Clean up handling of variable-free qual clauses. System now does the · 37168b8d
      Tom Lane authored
      right thing with variable-free clauses that contain noncachable functions,
      such as 'WHERE random() < 0.5' --- these are evaluated once per
      potential output tuple.  Expressions that contain only Params are
      now candidates to be indexscan quals --- for example, 'var = ($1 + 1)'
      can now be indexed.  Cope with RelabelType nodes atop potential indexscan
      variables --- this oversight prevents 7.0.* from recognizing some
      potentially indexscanable situations.
      37168b8d
  6. 08 Jun, 2000 1 commit
  7. 31 May, 2000 1 commit
  8. 30 May, 2000 1 commit
  9. 28 May, 2000 1 commit
    • Tom Lane's avatar
      First round of changes for new fmgr interface. fmgr itself and the · 0a7fb4e9
      Tom Lane authored
      key call sites are changed, but most called functions are still oldstyle.
      An exception is that the PL managers are updated (so, for example, NULL
      handling now behaves as expected in plperl and plpgsql functions).
      NOTE initdb is forced due to added column in pg_proc.
      0a7fb4e9
  10. 12 Apr, 2000 1 commit
  11. 23 Mar, 2000 2 commits
  12. 17 Mar, 2000 1 commit
  13. 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
  14. 24 Jan, 2000 1 commit
    • Tom Lane's avatar
      First cut at making useful selectivity estimates for range queries · 0dbffa70
      Tom Lane authored
      (ie, WHERE x > lowbound AND x < highbound).  It's not very bright yet
      but it does something useful.  Also, rename intltsel/intgtsel to
      scalarltsel/scalargtsel to reflect usage better.  Extend convert_to_scalar
      to do something a little bit useful with string data types.  Still need
      to make it do something with date/time datatypes, but I'll wait for
      Thomas's datetime unification dust to settle first.  Eventually the
      routine ought not have any type-specific knowledge at all; it ought to
      be calling a type-dependent routine found via a pg_type column; but
      that's a task for another day.
      0dbffa70
  15. 23 Jan, 2000 1 commit
  16. 09 Jan, 2000 1 commit
  17. 09 Sep, 1999 1 commit
    • Tom Lane's avatar
      Repair error noticed by Roberto Cornacchia: selectivity code · 51db6455
      Tom Lane authored
      was rejecting negative attnums as bogus, which of course they are not.
      Add code to get_attdisbursion to produce a useful value for OID attribute,
      since VACUUM does not store stats for system attributes.
      Also, repair bug that's been in eqjoinsel for a long time: it was taking
      the max of the two columns' disbursions, whereas it should use the min.
      51db6455
  18. 25 Jul, 1999 1 commit
  19. 24 Jul, 1999 1 commit
    • Tom Lane's avatar
      Clean up messy clause-selectivity code in clausesel.c; repair bug · ac4913a0
      Tom Lane authored
      identified by Hiroshi (incorrect cost attributed to OR clauses
      after multiple passes through set_rest_selec()).  I think the code
      was trying to allow selectivities of OR subclauses to be passed in
      from outside, but noplace was actually passing any useful data, and
      set_rest_selec() was passing wrong data.
      
      Restructure representation of "indexqual" in IndexPath nodes so that
      it is the same as for indxqual in completed IndexScan nodes: namely,
      a toplevel list with an entry for each pass of the index scan, having
      sublists that are implicitly-ANDed index qual conditions for that pass.
      You don't want to know what the old representation was :-(
      
      Improve documentation of OR-clause indexscan functions.
      
      Remove useless 'notclause' field from RestrictInfo nodes.  (This might
      force an initdb for anyone who has stored rules containing RestrictInfos,
      but I do not think that RestrictInfo ever appears in completed plans.)
      ac4913a0
  20. 16 Jul, 1999 2 commits
  21. 15 Jul, 1999 1 commit
  22. 25 May, 1999 1 commit
  23. 16 May, 1999 1 commit
  24. 15 Feb, 1999 1 commit
  25. 13 Feb, 1999 1 commit
  26. 03 Feb, 1999 2 commits
  27. 09 Nov, 1998 1 commit
  28. 01 Sep, 1998 2 commits
  29. 09 Aug, 1998 1 commit
  30. 01 Aug, 1998 1 commit
  31. 18 Jul, 1998 1 commit
  32. 15 Jun, 1998 1 commit
  33. 27 Apr, 1998 1 commit
    • Bruce Momjian's avatar
      This patch... · 09baa3cc
      Bruce Momjian authored
      1. Removes the unnecessary "#define AbcRegProcedure 123"'s from
      pg_proc.h.
      
      2. Changes those #defines to use the names already defined in
      fmgr.h.
      
      3. Forces the make of fmgr.h in backend/Makefile instead of having
      it
         made as a dependency in access/common/Makefile  *hack*hack*hack*
      
      4. Rearranged the #includes to a less helter-skelter arrangement,
      also
          changing <file.h> to "file.h" to signify a non-system header.
      
      5. Removed "pg_proc.h" from files where its only purpose was for
      the
         #defines removed in item #1.
      
      6. Added "fmgr.h" to each file changed for completeness sake.
      
      Turns out that #6 was not necessary for some files because fmgr.h
      was being included in a roundabout way SIX levels deep by the first
      include.
      
      "access/genam.h"
       ->"access/relscan.h"
         ->"utils/rel.h"
           ->"access/strat.h"
             ->"access/skey.h"
      	 ->"fmgr.h"
      
      So adding fmgr.h really didn't add anything to the compile, hopefully
      just made it clearer to the programmer.
      
      S Darren.
      09baa3cc
  34. 26 Feb, 1998 1 commit
  35. 13 Feb, 1998 1 commit
  36. 08 Sep, 1997 1 commit