1. 03 5月, 2000 8 次提交
  2. 02 5月, 2000 2 次提交
  3. 01 5月, 2000 2 次提交
    • T
      Reset CurrentMemoryContext to TopMemoryContext at the beginning of error · f6a3b87c
      Tom Lane 提交于
      cleanup, ie, as soon as we have caught the longjmp.  This ensures that
      current context will be a valid context throughout error cleanup.  Before
      it was possible that current context was pointing at a context that would
      get deleted during cleanup, leaving any subsequent pallocs in deep
      trouble.  I was able to provoke an Assert failure when compiled with
      asserts + -DCLOBBER_FREED_MEMORY, if I did something that would cause
      an error to be reported by the backend large-object code, because indeed
      that code operates in a context that gets deleted partway through xact
      abort --- and CurrentMemoryContext was still pointing at it!  Boo hiss.
      f6a3b87c
    • T
      Remove bogus 'xid loop detected' check, which actually wasn't detecting · e0095c6c
      Tom Lane 提交于
      loops, but just arbitrarily failing at 1000 locks.
      e0095c6c
  4. 29 4月, 2000 6 次提交
  5. 28 4月, 2000 8 次提交
  6. 27 4月, 2000 6 次提交
  7. 26 4月, 2000 8 次提交