1. 31 Jan, 2000 1 commit
  2. 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
  3. 25 Jan, 2000 1 commit
    • Bruce Momjian's avatar
      as attache of this mail is patch (to the main tree) with to_char's · b866d2e2
      Bruce Momjian authored
      family functions. Contain:
      
        conversion from a datetype to formatted text:
      
      	to_char( datetime, 	text)
      	to_char( timestamp,	text)
      	to_char( int4,		text)
      	to_char( int8,		text)
      	to_char( float4,	text)
      	to_char( float8,	text)
      	to_char( numeric,	text)
      
        vice versa:
      
      	to_date		( text, text)
      	to_datetime	( text, text)
      	to_timestamp	( text, text)
      	to_number	( text, text)	   (convert to numeric)
      
      
        PostgreSQL to_char is very compatible with Oracle's to_char(), but not
      total exactly (now). Small differentions are in number formating. It will
      fix in next to_char() version.
      
      
      ! If will this patch aplly to the main tree, must be delete the current
        to_char version in contrib (directory "dateformat" and note in contrib's
        README), this patch not erase it (sorry Bruce).
      
      
      
      The patch patching files:
      
      	doc/src/sgml/func.sgml
                           ^^^^^^^^
         Hmm, I'm not sure if my English... :( Check it anyone (volunteer)?
      
         Thomas, it is right? SGML is not my primary lang  and compile
         the current PG docs tree is very happy job (hard variables setting in
         docs/sgml/Makefile --> HSTYLE= /home/users/t/thomas/....  :-)
      
         What add any definition to global configure.in and set Makefiles in docs
         tree via ./configure?
      
      	src/backend/utils/adt/Makefile
      	src/backend/utils/adt/formatting.c
      	src/include/catalog/pg_proc.h
      	src/include/utils/formatting.h
      Karel Zak <zakkr@zf.jcu.cz>              http://home.zf.jcu.cz/~zakkr/
      b866d2e2
  4. 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
  5. 22 Jan, 2000 1 commit
  6. 18 Jan, 2000 1 commit
  7. 17 Jan, 2000 1 commit
  8. 10 Jan, 2000 1 commit
  9. 06 Jan, 2000 1 commit
  10. 28 Dec, 1999 1 commit
  11. 12 Dec, 1999 1 commit
    • Bruce Momjian's avatar
      I'm in TODO mood today ... · cb00b7fa
      Bruce Momjian authored
      * Document/trigger/rule so changes to pg_shadow recreate pg_pwd
      
      I did it with a trigger and it seems to work like a charm. The function
      that already updates the file for create and alter user has been made a
      built-in "SQL" function and a trigger is created at initdb time.
      
      Comments around the pg_pwd updating function seem to be worried about
      this
      routine being called concurrently, but I really don't see a reason to
      worry about this. Verify for yourself. I guess we never had a system
      trigger before, so treat this with care, and feel free to adjust the
      nomenclature as well.
      
      --
      Peter Eisentraut                  Sernanders väg 10:115
      cb00b7fa
  12. 01 Dec, 1999 1 commit
  13. 25 Nov, 1999 1 commit
  14. 17 Nov, 1999 1 commit
  15. 11 Oct, 1999 1 commit
  16. 30 Sep, 1999 1 commit
  17. 29 Sep, 1999 1 commit
  18. 26 Sep, 1999 1 commit
    • Tom Lane's avatar
      Implement constant-expression simplification per Bernard · 40f65241
      Tom Lane authored
      Frankpitt, plus some improvements from yours truly.  The simplifier depends
      on the proiscachable field of pg_proc to tell it whether a function is
      safe to pre-evaluate --- things like nextval() are not, for example.
      Update pg_proc.h to contain reasonable cacheability information; as of
      6.5.* hardly any functions were marked cacheable.  I may have erred too
      far in the other direction; see recent mail to pghackers for more info.
      This update does not force an initdb, exactly, but you won't see much
      benefit from the simplifier until you do one.
      40f65241
  19. 29 Aug, 1999 1 commit
    • Tom Lane's avatar
      Correct broken entries for pg_proc OIDs 1364 (time(abstime)) · 1f14a9de
      Tom Lane authored
      and 1370 (timestamp(datetime)).  This does not force an initdb, exactly,
      but you won't see the effects of the bug fix until you do one.
      BTW, OID 1358 for timespan(time) is still broken:
      select timespan('21:11:26'::time);
      ERROR:  No such function 'time_timespan' with the specified attributes
      But I couldn't figure out what it ought to be defined as, so I left it be.
      1f14a9de
  20. 15 Jul, 1999 1 commit
  21. 25 May, 1999 1 commit
  22. 09 May, 1999 1 commit
  23. 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
  24. 20 Apr, 1999 1 commit
  25. 13 Apr, 1999 1 commit
  26. 29 Mar, 1999 1 commit
    • Tom Lane's avatar
      Modify fmgr so that internal name (compiler name) of a built-in · c537d429
      Tom Lane authored
      function is found in prosrc field of pg_proc, not proname.  This allows
      multiple aliases of a built-in to all be implemented as direct builtins,
      without needing a level of indirection through an SQL function.  Replace
      existing SQL alias functions with builtin entries accordingly.
      Save a few K by not storing string names of builtin functions in fmgr's
      internal table (if you really want 'em, get 'em from pg_proc...).
      Update opr_sanity with a few more cross-checks.
      c537d429
  27. 28 Mar, 1999 1 commit
  28. 14 Mar, 1999 2 commits
  29. 10 Mar, 1999 1 commit
    • Tom Lane's avatar
      Fix some typos in argument and result types in pg_proc · 3bca9c6c
      Tom Lane authored
      and pg_operator.  The lone error in pg_operator was reported as a bug
      by Michael Reifenberger; the multiple errors in pg_proc would only have
      been noticed if one invoked the functions by name rather than using
      operator syntax.  I guess few people do that.
      3bca9c6c
  30. 13 Feb, 1999 2 commits
  31. 30 Dec, 1998 1 commit
  32. 13 Dec, 1998 1 commit
  33. 08 Dec, 1998 1 commit
  34. 17 Nov, 1998 1 commit
  35. 29 Oct, 1998 2 commits
  36. 22 Oct, 1998 2 commits