Re: [EXT] Re: log_min_messages = warning

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Dirschel, Steve" <steve(dot)dirschel(at)thomsonreuters(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: [EXT] Re: log_min_messages = warning
Date: 2022-09-06 20:44:29
Message-ID: 3355583.1662497069@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Dirschel, Steve" <steve(dot)dirschel(at)thomsonreuters(dot)com> writes:
>>> We recently upgraded from postgres 12.8 to 14.3.  We are running
>>> Aurora Postgres on AWS.

Aurora Postgres != Postgres. This doesn't seem like something they'd
change, but we can't rule that out entirely.

>> Try:
>> select setting, source, sourcefile, pending_restart from pg_settings where name = 'log_min_messages';

> shgroup02s=> select setting, source, sourcefile, pending_restart from pg_settings where name = 'log_min_messages';
> setting | source | sourcefile | pending_restart
> ---------+---------+------------+-----------------
> warning | default | | f
> (1 row)

OK, so log_min_messages has the expected value in your interactive
session, and yet evidently not in the sessions running these RAISE NOTICE
commands. Maybe you have done ALTER USER SET or ALTER DATABASE SET
commands that'd change it in those sessions? You could look in
the pg_db_role_setting catalog to answer that definitively.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron 2022-09-06 20:52:43 Re: Feature proposal: immutable/sealed partitions (and maybe tables, too)
Previous Message Dirschel, Steve 2022-09-06 19:54:33 RE: [EXT] Re: log_min_messages = warning