1. 08 Oct, 2002 1 commit
  2. 06 Oct, 2002 1 commit
  3. 27 Sep, 2002 2 commits
  4. 26 Sep, 2002 1 commit
  5. 25 Sep, 2002 1 commit
    • Tom Lane's avatar
      Remove ShutdownBufferPoolAccess exit callback, and do the work in · 8a6fab41
      Tom Lane authored
      ProcKill instead, where we still have a PGPROC with which to wait on
      LWLocks.  This fixes 'can't wait without a PROC structure' failures
      occasionally seen during backend shutdown (I'm surprised they weren't
      more frequent, actually).  Add an Assert() to LWLockAcquire to help
      catch any similar mistakes in future.  Fix failure to update MyProcPid
      for standalone backends and pgstat processes.
      8a6fab41
  6. 20 Sep, 2002 1 commit
    • Bruce Momjian's avatar
      > I'm not sure why NDirectFileRead/NDirectFileWrite are unused at the · a834cbe1
      Bruce Momjian authored
      > moment, but they used to be used; I think the correct response is to
      > put back the missing counter increments, not rip out the counters.
      
      Ok, fair enough. It's worth noting that they've been broken for a
      while -- for example, the HashJoin counter increments were broken when
      you comitted r1.20 of executor/nodeHashJoin.c in May of '99.
      
      I've attached a revised patch that doesn't remove the counters (but
      doesn't increment them either: I'm not sure of all the places where
      the counter should be incremented).
      
      Neil Conway
      a834cbe1
  7. 16 Sep, 2002 1 commit
    • Tom Lane's avatar
      Fix for rare race-condition-like failure: if a backend receives SIGUSR2 · 53e95eee
      Tom Lane authored
      (notify/SI-overrun interrupt) while it is in process of doing proc_exit,
      it is possible for Async_NotifyHandler() to try to start a transaction
      when one is already running.  This leads to Asserts() or worse.  I think
      it may only be possible to occur when frontend synchronization is lost
      (ie, the elog(FATAL) in SocketBackend() fires), but that is a standard
      occurrence after error during COPY.  In any case, I have seen this
      failure occur during regression tests, so it is definitely possible.
      53e95eee
  8. 04 Sep, 2002 1 commit
  9. 02 Sep, 2002 2 commits
  10. 01 Sep, 2002 1 commit
  11. 30 Aug, 2002 1 commit
    • Tom Lane's avatar
      AUTOCOMMIT mode is now an available backend GUC variable; setting it · 26993b29
      Tom Lane authored
      to false provides more SQL-spec-compliant behavior than we had before.
      I am not sure that setting it false is actually a good idea yet; there
      is a lot of client-side code that will probably be broken by turning
      autocommit off.  But it's a start.
      
      Loosely based on a patch by David Van Wie.
      26993b29
  12. 29 Aug, 2002 2 commits
  13. 27 Aug, 2002 1 commit
  14. 17 Aug, 2002 1 commit
  15. 15 Aug, 2002 1 commit
    • Bruce Momjian's avatar
      Tom Lane wrote: · b1a5f872
      Bruce Momjian authored
      > There's no longer a separate call to heap_storage_create in that routine
      > --- the right place to make the test is now in the storage_create
      > boolean parameter being passed to heap_create.  A simple change, but
      > it passeth patch's understanding ...
      
      Thanks.
      
      Attached is a patch against cvs tip as of 8:30 PM PST or so. Turned out
      that even after fixing the failed hunks, there was a new spot in
      bufmgr.c which needed to be fixed (related to temp relations;
      RelationUpdateNumberOfBlocks). But thankfully the regression test code
      caught it :-)
      
      Joe Conway
      b1a5f872
  16. 10 Aug, 2002 1 commit
    • Bruce Momjian's avatar
      This patch removes a lot of unused code related to assertions and · c5354dff
      Bruce Momjian authored
      error handling, and simplifies the code that remains. Apparently,
      the code that left Berkeley had a whole "error handling subsystem",
      which exceptions and whatnot. Since we don't use that anymore,
      there's no reason to keep it around.
      
      The regression tests pass with the patch applied. Unless anyone
      sees a problem, please apply.
      
      Neil Conway
      c5354dff
  17. 06 Aug, 2002 1 commit
    • Bruce Momjian's avatar
      This patch changes the behavior of PostgreSQL so that if any queries are · a6c76819
      Bruce Momjian authored
      executed in an implicitely aborted transaction (e.g. after an occur
      occurs), we return an error (and not just a warning). For example:
      
      nconway=# begin;
      BEGIN
      nconway=# insert; -- syntax error
      ERROR:  parser: parse error at or near ";"
      nconway=# select * from a;
      ERROR:  current transaction is aborted, queries ignored until end of
      transaction block
      
      The old behavior was:
      
      nconway=# begin;
      BEGIN
      nconway=# insert;
      ERROR:  parser: parse error at or near ";"
      nconway=# select * from a;
      WARNING:  current transaction is aborted, queries ignored until end
      of transaction block
      *ABORT STATE*
      
      Which can be confusing: if the client isn't paying careful attention,
      they will conclude that the query has executed (because no error is
      returned).
      
      Neil Conway
      a6c76819
  18. 04 Aug, 2002 3 commits
  19. 30 Jul, 2002 3 commits
  20. 29 Jul, 2002 1 commit
    • Tom Lane's avatar
      Implement CREATE/DROP OPERATOR CLASS. Work still remains: need more · ea4686e3
      Tom Lane authored
      documentation (xindex.sgml should be rewritten), need to teach pg_dump
      about it, need to update contrib modules that currently build pg_opclass
      entries by hand.  Original patch by Bill Studenmund, grammar adjustments
      and general update for 7.3 by Tom Lane.
      ea4686e3
  21. 18 Jul, 2002 2 commits
  22. 13 Jul, 2002 1 commit
  23. 11 Jul, 2002 1 commit
    • Tatsuo Ishii's avatar
      Add new CREATE CONVERSION/DROP CONVERSION command. · fcc96256
      Tatsuo Ishii authored
      This is the first cut toward CREATE CONVERSION/DROP CONVERSION implementaion.
      The commands can now add/remove tuples to the new pg_conversion system
      catalog, but that's all. Still need work to make them actually working.
      Documentations, regression tests also need work.
      fcc96256
  24. 20 Jun, 2002 1 commit
  25. 18 May, 2002 1 commit
  26. 17 May, 2002 2 commits
  27. 10 May, 2002 1 commit
  28. 05 May, 2002 1 commit
  29. 20 Apr, 2002 1 commit
    • Peter Eisentraut's avatar
      Scanner performance improvements · 32c6c99e
      Peter Eisentraut authored
      Use flex flags -CF.  Pass the to-be-scanned string around as StringInfo
      type, to avoid querying the length repeatedly.  Clean up some code and
      remove lex-compatibility cruft.  Escape backslash sequences inline.  Use
      flex-provided yy_scan_buffer() function to set up input, rather than using
      myinput().
      32c6c99e
  30. 18 Apr, 2002 1 commit
    • Tom Lane's avatar
      Rule names are now unique per-relation, rather than unique globally. · b3120804
      Tom Lane authored
      DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause,
      similar to TRIGGER syntaxes.  To allow loading of existing pg_dump
      files containing COMMENT ON RULE, the COMMENT code will still accept
      the old syntax --- but only if the target rulename is unique across
      the whole database.
      b3120804
  31. 24 Mar, 2002 1 commit