Avoid cluttering the postmaster log with bogus complaints
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 14 Jan 2008 19:18:53 +0000 (19:18 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 14 Jan 2008 19:18:53 +0000 (19:18 +0000)
during transaction abort, per my note from a couple days ago.

src/backend/utils/misc/guc.c

index 47c8b6259d8b8966871f773d003d711df4775a6f..acd0900d962347ee7d12ba802dbaa3d2ec29dbe3 100644 (file)
@@ -4829,6 +4829,16 @@ GUC_complaint_elevel(GucSource source)
                 */
                elevel = IsUnderPostmaster ? DEBUG3 : LOG;
        }
+       else if (source == PGC_S_OVERRIDE)
+       {
+               /*
+                * If we're a postmaster child, this is probably "undo" during
+                * transaction abort, so we don't want to clutter the log.  There's
+                * a small chance of a real problem with an OVERRIDE setting,
+                * though, so suppressing the message entirely wouldn't be desirable.
+                */
+               elevel = IsUnderPostmaster ? DEBUG5 : LOG;
+       }
        else if (source < PGC_S_INTERACTIVE)
                elevel = LOG;
        else