1. 10 9月, 2004 14 次提交
  2. 09 9月, 2004 12 次提交
  3. 08 9月, 2004 1 次提交
  4. 07 9月, 2004 6 次提交
  5. 06 9月, 2004 3 次提交
  6. 05 9月, 2004 2 次提交
    • T
      On further consideration, there's another problem here: the existing · 1a86e6ea
      Tom Lane 提交于
      elog() emulation code always calls errstart with ERROR error level.
      This means that a recursive error call triggered by elog would do
      MemoryContextReset(ErrorContext), whether or not this was actually
      appropriate.  I'm surprised we haven't seen this in the field...
      1a86e6ea
    • T
      Tweak elog.c's logic for promoting errors into more severe errors. · cefb4b14
      Tom Lane 提交于
      Messages of less than ERROR severity should never be promoted (this
      fixes Gaetano Mendola's problem with a COMMERROR becoming a PANIC,
      and is obvious in hindsight anyway).  Do all promotion in errstart
      not errfinish, to ensure that output decisions are made correctly;
      the former coding could suppress logging of promoted errors, which
      doesn't seem like a good idea.  Eliminate some redundant code too.
      cefb4b14
  7. 03 9月, 2004 2 次提交