Skip to content
Snippets Groups Projects
  1. Sep 08, 2004
  2. Sep 07, 2004
  3. Sep 06, 2004
  4. Sep 05, 2004
    • Tom Lane's avatar
      On further consideration, there's another problem here: the existing · 1a86e6ea
      Tom Lane authored
      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
    • Tom Lane's avatar
      Tweak elog.c's logic for promoting errors into more severe errors. · cefb4b14
      Tom Lane authored
      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
  5. Sep 03, 2004
  6. Sep 02, 2004
  7. Sep 01, 2004
Loading