1. 02 Nov, 2001 1 commit
  2. 31 Oct, 2001 1 commit
  3. 25 Oct, 2001 1 commit
  4. 22 Oct, 2001 1 commit
  5. 19 Oct, 2001 1 commit
  6. 18 Oct, 2001 1 commit
  7. 15 Oct, 2001 2 commits
    • Tom Lane's avatar
      e158670c
    • Bruce Momjian's avatar
      > Uh, isn't the correct fix · 394925b6
      Bruce Momjian authored
       > ! $$ = cat_str(8, make_str("grant"), $2, make_str("on"), $4, $5,
       > make_str("to"), $7, $8);
       > ISTM your patch loses the opt_with_grant clause.  (Of course the
       > backend doesn't currently accept that clause anyway, but that's no
       > reason for ecpg to drop it.)
      
      My patch doesn't loose the option, it's never been passed on anyway:
      
       opt_with_grant:  WITH GRANT OPTION
                                      {
                                              mmerror(ET_ERROR, "WITH GRANT OPTION is not supported.  Only relation owners can
       set privileges");
                                       }
                      | /*EMPTY*/
                      ;
      
      The existing code in ecpg/preproc/preproc.y to handle the WITH option
      simply throws an error and aborts the processing... The patch below
      prevents the segfault and also passes on the WITH option to the
      backend, probably a better fix.
      
      Lee Kindness
      394925b6
  8. 14 Oct, 2001 1 commit
  9. 05 Oct, 2001 1 commit
  10. 03 Oct, 2001 1 commit
  11. 02 Oct, 2001 1 commit
  12. 01 Oct, 2001 1 commit
  13. 25 Sep, 2001 1 commit
  14. 19 Sep, 2001 1 commit
  15. 19 Aug, 2001 1 commit
  16. 16 Aug, 2001 1 commit
    • Tom Lane's avatar
      Sequences are now based on int8, not int4, arithmetic. SERIAL pseudo-type · d4f4b971
      Tom Lane authored
      has an alias SERIAL4 and a sister SERIAL8.  SERIAL8 is just the same
      except the created column is type int8 not int4.
      initdb forced.  Note this also breaks any chance of pg_upgrade from 7.1,
      unless we hack up pg_upgrade to drop and recreate sequences.  (Which is
      not out of the question, but I don't wanna do it.)
      d4f4b971
  17. 10 Aug, 2001 2 commits
  18. 04 Aug, 2001 2 commits
  19. 16 Jul, 2001 1 commit
  20. 12 Jul, 2001 1 commit
  21. 11 Jul, 2001 1 commit
  22. 10 Jul, 2001 1 commit
    • Tom Lane's avatar
      Changes from Vince Vielhaber to allow the optional clauses of CREATE · 320b6db0
      Tom Lane authored
      USER and ALTER USER to appear in any order, not only the fixed order
      they used to be required to appear in.
      Also, some changes from Tom Lane to create a FULL option for VACUUM;
      it doesn't do anything yet, but I needed to change many of the same
      files to make that happen, so now seemed like a good time.
      320b6db0
  23. 09 Jul, 2001 1 commit
  24. 23 Jun, 2001 1 commit
  25. 13 Jun, 2001 1 commit
  26. 01 Jun, 2001 1 commit
  27. 07 May, 2001 1 commit
    • Tom Lane's avatar
      Rewrite of planner statistics-gathering code. ANALYZE is now available as · f905d65e
      Tom Lane authored
      a separate statement (though it can still be invoked as part of VACUUM, too).
      pg_statistic redesigned to be more flexible about what statistics are
      stored.  ANALYZE now collects a list of several of the most common values,
      not just one, plus a histogram (not just the min and max values).  Random
      sampling is used to make the process reasonably fast even on very large
      tables.  The number of values and histogram bins collected is now
      user-settable via an ALTER TABLE command.
      
      There is more still to do; the new stats are not being used everywhere
      they could be in the planner.  But the remaining changes for this project
      should be localized, and the behavior is already better than before.
      
      A not-very-related change is that sorting now makes use of btree comparison
      routines if it can find one, rather than invoking '<' twice.
      f905d65e
  28. 01 May, 2001 1 commit
  29. 05 Apr, 2001 1 commit
  30. 26 Feb, 2001 1 commit
  31. 19 Feb, 2001 1 commit
  32. 10 Feb, 2001 1 commit
    • Tom Lane's avatar
      Restructure the key include files per recent pghackers discussion: there · d08741ea
      Tom Lane authored
      are now separate files "postgres.h" and "postgres_fe.h", which are meant
      to be the primary include files for backend .c files and frontend .c files
      respectively.  By default, only include files meant for frontend use are
      installed into the installation include directory.  There is a new make
      target 'make install-all-headers' that adds the whole content of the
      src/include tree to the installed fileset, for use by people who want to
      develop server-side code without keeping the complete source tree on hand.
      Cleaned up a whole lot of crufty and inconsistent header inclusions.
      d08741ea
  33. 25 Jan, 2001 1 commit
  34. 22 Jan, 2001 1 commit
  35. 09 Jan, 2001 1 commit
  36. 05 Jan, 2001 1 commit
    • Tom Lane's avatar
      Remove not-really-standard implementation of CREATE TABLE's UNDER clause, · 2fb6cc90
      Tom Lane authored
      and revert documentation to describe the existing INHERITS clause
      instead, per recent discussion in pghackers.  Also fix implementation
      of SQL_inheritance SET variable: it is not cool to look at this var
      during the initial parsing phase, only during parse_analyze().  See
      recent bug report concerning misinterpretation of date constants just
      after a SET TIMEZONE command.  gram.y really has to be an invariant
      transformation of the query string to a raw parsetree; anything that
      can vary with time must be done during parse analysis.
      2fb6cc90
  37. 22 Dec, 2000 1 commit