1. 24 Sep, 2004 1 commit
  2. 16 Aug, 2004 1 commit
  3. 08 Aug, 2004 2 commits
  4. 31 Jul, 2004 2 commits
    • Tom Lane's avatar
      Support "OR condition ..." in plpgsql EXCEPTION clauses to make the syntax · 9c8d0850
      Tom Lane authored
      more nearly Oracle-equivalent.  Allow matching by category as well as
      specific error code.  Document the set of available condition names
      (or more accurately, synchronize it with the existing documentation).  In
      passing, update errcodes.sgml to include codes added during 7.5 development.
      9c8d0850
    • Tom Lane's avatar
      plpgsql does exceptions. · beda4814
      Tom Lane authored
      There are still some things that need refinement; in particular I fear
      that the recognized set of error condition names probably has little in
      common with what Oracle recognizes.  But it's a start.
      beda4814
  5. 11 Jul, 2004 2 commits
  6. 04 Jul, 2004 1 commit
    • Tom Lane's avatar
      Okay, I've had it with answering newbie questions about why plpgsql · a72dd7a9
      Tom Lane authored
      FOR loops are giving weird syntax errors.  Restructure parsing of FOR
      loops so that the integer-loop-vs-query-loop decision is driven off
      the presence of '..' between IN and LOOP, rather than the presence
      of a matching record/row variable name.  Hopefully this will make the
      behavior a bit more transparent.
      a72dd7a9
  7. 16 May, 2004 1 commit
  8. 26 Mar, 2004 1 commit
  9. 27 Feb, 2004 1 commit
  10. 03 Feb, 2004 1 commit
    • Tom Lane's avatar
      Rename SortMem and VacuumMem to work_mem and maintenance_work_mem. · 391c3811
      Tom Lane authored
      Make btree index creation and initial validation of foreign-key constraints
      use maintenance_work_mem rather than work_mem as their memory limit.
      Add some code to guc.c to allow these variables to be referenced by their
      old names in SHOW and SET commands, for backwards compatibility.
      391c3811
  11. 24 Jan, 2004 1 commit
  12. 22 Jan, 2004 1 commit
  13. 30 Nov, 2003 2 commits
  14. 29 Nov, 2003 1 commit
    • PostgreSQL Daemon's avatar
      · 969685ad
      PostgreSQL Daemon authored
      $Header: -> $PostgreSQL Changes ...
      969685ad
  15. 12 Nov, 2003 1 commit
  16. 01 Nov, 2003 1 commit
  17. 23 Sep, 2003 1 commit
  18. 12 Sep, 2003 1 commit
  19. 11 Sep, 2003 3 commits
  20. 03 Sep, 2003 1 commit
  21. 31 Aug, 2003 1 commit
  22. 09 Aug, 2003 1 commit
  23. 28 May, 2003 1 commit
    • Tom Lane's avatar
      Replace functional-index facility with expressional indexes. Any column · fc8d970c
      Tom Lane authored
      of an index can now be a computed expression instead of a simple variable.
      Restrictions on expressions are the same as for predicates (only immutable
      functions, no sub-selects).  This fixes problems recently introduced with
      inlining SQL functions, because the inlining transformation is applied to
      both expression trees so the planner can still match them up.  Along the
      way, improve efficiency of handling index predicates (both predicates and
      index expressions are now cached by the relcache) and fix 7.3 oversight
      that didn't record dependencies of predicate expressions.
      fc8d970c
  24. 27 Apr, 2003 1 commit
  25. 07 Apr, 2003 1 commit
  26. 25 Mar, 2003 1 commit
  27. 19 Feb, 2003 1 commit
    • Bruce Momjian's avatar
      This patch makes the following changes to the documentation: · cde8bbc4
      Bruce Momjian authored
      - more work from the SGML police
      
      - some grammar improvements: rewriting a paragraph or two, replacing
      contractions where (IMHO) appropriate
      
      - fix missing utility commands in lock mode docs
      
      - improve CLUSTER, REINDEX, SET SESSION AUTHORIZATION ref pages
      
      Neil Conway
      cde8bbc4
  28. 19 Jan, 2003 1 commit
    • Bruce Momjian's avatar
      This patch includes a lot of minor cleanups to the SGML documentation, · be2b660e
      Bruce Momjian authored
      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
  29. 15 Jan, 2003 1 commit
  30. 23 Nov, 2002 1 commit
    • Bruce Momjian's avatar
      This patch implements FOR EACH STATEMENT triggers, per my email to · 1b7f3cc0
      Bruce Momjian authored
      -hackers a couple days ago.
      
      Notes/caveats:
      
              - added regression tests for the new functionality, all
                regression tests pass on my machine
      
              - added pg_dump support
      
              - updated PL/PgSQL to support per-statement triggers; didn't
                look at the other procedural languages.
      
              - there's (even) more code duplication in trigger.c than there
                was previously. Any suggestions on how to refactor the
                ExecXXXTriggers() functions to reuse more code would be
                welcome -- I took a brief look at it, but couldn't see an
                easy way to do it (there are several subtly-different
                versions of the code in question)
      
              - updated the documentation. I also took the liberty of
                removing a big chunk of duplicated syntax documentation in
                the Programmer's Guide on triggers, and moving that
                information to the CREATE TRIGGER reference page.
      
              - I also included some spelling fixes and similar small
                cleanups I noticed while making the changes. If you'd like
                me to split those into a separate patch, let me know.
      
      Neil Conway
      1b7f3cc0
  31. 15 Nov, 2002 1 commit
  32. 14 Nov, 2002 1 commit
  33. 10 Nov, 2002 1 commit
    • Bruce Momjian's avatar
      This patch makes a minor cleanup to the implementation of PERFORM in · cfd27281
      Bruce Momjian authored
      PL/PgSQL. Previously, it had been bundled together with the assign
      statement implementation, for some reason that wasn't clear to me
      (they certainly don't share any code with one another). So I separated
      them and made PERFORM a statement like any other. No changes in
      functionality.
      
      Along the way, I added some regression tests for PERFORM, added a
      bunch more SGML tags to the PL/PgSQL docs, and removed an obsolete
      comment relating to the implementation of RETURN NEXT.
      
      Neil Conway
      cfd27281
  34. 21 Sep, 2002 1 commit