| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: I am done |
| Date: | 2002-09-05 15:25:38 |
| Message-ID: | 200209051525.g85FPcL07235@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> There's some value in being able to kick the log level up a notch for
> a specific session, but knocking it down from the admin's default could
> be considered a bad thing. I suppose we could invent a PGC_SIGHUP
> "min_server_min_messages" variable that sets a minimum value below which
> the user can't set server_min_messages. Does that seem like a good
> idea, or overkill?
>
> A compromise position would be to make these two variables PG_SUSET,
> ie settable per-session but only if you're superuser.
Oh, I just saw your compromise position. Yes, I think that is the way
to go.
In fact, aside from the security issue, allowing users to throw
voluminous debug info into the server logs doesn't seem like a good idea
anyway.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2002-09-05 15:27:23 | Re: 7.2 - 7.3 activity |
| Previous Message | Bruce Momjian | 2002-09-05 15:21:18 | Re: I am done |