Re: Bug #928: server_min_messages (log_min_messages in CVS) have - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: Bug #928: server_min_messages (log_min_messages in CVS) have
Date
Msg-id 200303310020.h2V0KTc21863@candle.pha.pa.us
Whole thread Raw
In response to Re: Bug #928: server_min_messages (log_min_messages in CVS) have PGC_USERSET GucContext  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug #928: server_min_messages (log_min_messages in CVS)  (Neil Conway <neilc@samurai.com>)
List pgsql-bugs
Tom Lane wrote:
> pgsql-bugs@postgresql.org writes:
> > In src/backend/utils/misc/guc.c "server_min_messages"
> > ("log_min_messages" in CVS)configuration option have PGC_USERSET
> > GucContext. I think that it is not good idea that user can
> > change server log details level. I suggest change GucContext in
> > this case on PGC_SIGHUP.
>
> PGC_SUSET would be appropriate if we think that there's really a security
> issue here.  But ISTM this was already considered when the present setup
> was designed, and we deliberately chose USERSET.  Bruce, do you remember
> what the reasoning was?

The issue was that you might want to increase server logging in certain
clients to help debug a problem.  If we had a "don't raise me" setting,
that would work.

Another idea is to add the ability to SET things perminantly.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug #928: server_min_messages (log_min_messages in CVS) have PGC_USERSET GucContext
Next
From: Tom Lane
Date:
Subject: Re: Bug #922: PANIC: open of /scratch/production_2/pg_clog/0996 failed: No such file or directory