log_min_messages = warning

From: "Dirschel, Steve" <steve(dot)dirschel(at)thomsonreuters(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: log_min_messages = warning
Date: 2022-09-06 19:07:56
Message-ID: DM6PR03MB433216774DF79FF496ADB14DFA7E9@DM6PR03MB4332.namprd03.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

We recently upgraded from postgres 12.8 to 14.3. We are running Aurora Postgres on AWS.

We have procedures that will make calls to RAISE NOTICE to write out messages if you interactively call the procedure through psql. These procedures are getting called by pg_cron.

Since upgrading these RAISE NOTICE messages are getting written to the postgres log file:

For example:

13:45:00.720882-05
CONTEXT: PL/pgSQL function perf.snap_stats() line 242 at RAISE
2022-09-06 18:45:01 UTC::@:[21535]:LOG: cron job 2: NOTICE: Snapping dba_hist_system_event at 2022-09-06 13:45:00.725818-05

Log_min_messages is set to warning so my understanding is that should only log messages at warning, error, log, fatal, or panic. Any idea how to troubleshoot why these are getting written to the log file?

Thanks
This e-mail is for the sole use of the intended recipient and contains information that may be privileged and/or confidential. If you are not an intended recipient, please notify the sender by return e-mail and delete this e-mail and any attachments. Certain required legal entity disclosures can be accessed on our website: https://www.thomsonreuters.com/en/resources/disclosures.html

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Levi Aul 2022-09-06 19:39:37 Feature proposal: immutable/sealed partitions (and maybe tables, too)
Previous Message Jeffrey Walton 2022-09-06 14:13:29 Re: Determine if a user and database are available