1. 03 5月, 2003 1 次提交
    • T
      Portal and memory management infrastructure for extended query protocol. · de28dc9a
      Tom Lane 提交于
      Both plannable queries and utility commands are now always executed
      within Portals, which have been revamped so that they can handle the
      load (they used to be good only for single SELECT queries).  Restructure
      code to push command-completion-tag selection logic out of postgres.c,
      so that it won't have to be duplicated between simple and extended queries.
      initdb forced due to addition of a field to Query nodes.
      de28dc9a
  2. 26 3月, 2003 1 次提交
  3. 24 3月, 2003 1 次提交
  4. 19 1月, 2003 1 次提交
    • B
      This patch includes a lot of minor cleanups to the SGML documentation, · be2b660e
      Bruce Momjian 提交于
      including:
      
      - replacing all the appropriate usages of <citetitle>PostgreSQL
      ...</citetitle> with &cite-user;, &cite-admin;, and so on
      
      - fix an omission in the EXECUTE documentation
      
      - add some more text to the EXPLAIN documentation
      
      - improve the PL/PgSQL RETURN NEXT documentation (more work to do here)
      
      - minor markup fixes
      
      
      Neil Conway
      be2b660e
  5. 24 10月, 2002 1 次提交
  6. 12 10月, 2002 1 次提交
  7. 28 7月, 2002 1 次提交
  8. 22 4月, 2002 1 次提交
    • T
      Augment the date/time examples in the User's Guide to reflect the newer · c05f29e8
      Thomas G. Lockhart 提交于
       capabilities of specifying time zones as intervals per SQL9x.
      Put refentrytitle contents on the same line as the tag.
       Otherwise, leading whitespace is propagated into the product, which
       (at least) messes up the ToC layout.
      Remove (some) docinfo tags containing dates. Best to omit if the dates
       are not accurate; maybe use CVS dates instead or leave them out.
      c05f29e8
  9. 23 3月, 2002 1 次提交
  10. 03 3月, 2002 1 次提交
    • B
      Commit to match discussed elog() changes. Only update is that LOG is · a033daf5
      Bruce Momjian 提交于
      now just below FATAL in server_min_messages.  Added more text to
      highlight ordering difference between it and client_min_messages.
      
      ---------------------------------------------------------------------------
      
      REALLYFATAL => PANIC
      STOP => PANIC
      New INFO level the prints to client by default
      New LOG level the prints to server log by default
      Cause VACUUM information to print only to the client
      NOTICE => INFO where purely information messages are sent
      DEBUG => LOG for purely server status messages
      DEBUG removed, kept as backward compatible
      DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1 added
      DebugLvl removed in favor of new DEBUG[1-5] symbols
      New server_min_messages GUC parameter with values:
              DEBUG[5-1], INFO, NOTICE, ERROR, LOG, FATAL, PANIC
      New client_min_messages GUC parameter with values:
              DEBUG[5-1], LOG, INFO, NOTICE, ERROR, FATAL, PANIC
      Server startup now logged with LOG instead of DEBUG
      Remove debug_level GUC parameter
      elog() numbers now start at 10
      Add test to print error message if older elog() values are passed to elog()
      Bootstrap mode now has a -d that requires an argument, like postmaster
      a033daf5
  11. 08 12月, 2001 1 次提交
  12. 29 11月, 2001 1 次提交
  13. 25 11月, 2001 1 次提交
  14. 28 9月, 2001 1 次提交
  15. 08 9月, 2001 1 次提交
    • P
      Make the world somewhat safe for (not from) DELETE FROM pg_shadow; · c0d4d547
      Peter Eisentraut 提交于
      Assign the fixed user id 1 to the user created by initdb.
      A stand-alone backend will always set the user id to 1.
      (Consequently, the name of that user is no longer important.)
      
      In stand-alone mode, the user id 1 will have implicit superuser
      status, to allow repairs even if there are no users defined.
      
      Print a warning message when starting in stand-alone mode when no
      users are defined.
      
      Disallow dropping the current user and session user.
      
      Granting/revoking superuser status also grants/revokes usecatupd.
      (Previously, it would never grant it back.  This could lead to "deadlocks".)
      
      CREATE USER and CREATE GROUP will start allocating user ids at 100
      (unless explicitly specified), to prevent accidental creation of a
      superuser (plus some room for future extensions).
      c0d4d547
  16. 03 9月, 2001 1 次提交
  17. 18 3月, 2001 1 次提交
  18. 26 12月, 2000 1 次提交
  19. 15 11月, 2000 1 次提交
  20. 06 10月, 2000 1 次提交
  21. 22 7月, 2000 2 次提交
  22. 21 7月, 2000 2 次提交
  23. 09 5月, 2000 1 次提交
  24. 03 5月, 2000 1 次提交
  25. 28 3月, 2000 1 次提交
  26. 06 8月, 1999 1 次提交
  27. 22 7月, 1999 1 次提交
  28. 07 7月, 1999 1 次提交
  29. 14 6月, 1999 1 次提交
  30. 27 5月, 1999 2 次提交
  31. 23 5月, 1999 1 次提交
  32. 20 5月, 1999 1 次提交
  33. 18 3月, 1999 1 次提交
  34. 18 2月, 1999 1 次提交
  35. 24 8月, 1998 1 次提交
  36. 28 5月, 1998 1 次提交
  37. 26 1月, 1998 1 次提交
    • M
      From: Phil Thompson <phil@river-bank.demon.co.uk> · d5bbe2ac
      Marc G. Fournier 提交于
      I've completed the patch to fix the protocol and authentication issues I
      was discussing a couple of weeks ago.  The particular changes are:
      
      - the protocol has a version number
      - network byte order is used throughout
      - the pg_hba.conf file is used to specify what method is used to
        authenticate a frontend (either password, ident, trust, reject, krb4
        or krb5)
      - support for multiplexed backends is removed
      - appropriate changes to man pages
      - the -a switch to many programs to specify an authentication service
        no longer has any effect
      - the libpq.so version number has changed to 1.1
      
      The new backend still supports the old protocol so old interfaces won't
      break.
      d5bbe2ac