Skip to content
Snippets Groups Projects
  1. May 05, 2000
  2. May 04, 2000
  3. May 03, 2000
  4. May 02, 2000
  5. Apr 30, 2000
    • Tom Lane's avatar
      Reset CurrentMemoryContext to TopMemoryContext at the beginning of error · f6a3b87c
      Tom Lane authored
      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
    • Tom Lane's avatar
      Remove bogus 'xid loop detected' check, which actually wasn't detecting · e0095c6c
      Tom Lane authored
      loops, but just arbitrarily failing at 1000 locks.
      e0095c6c
  6. Apr 29, 2000
  7. Apr 28, 2000
  8. Apr 27, 2000
  9. Apr 26, 2000
Loading