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:30:08 |
Message-ID: | 200209051530.g85FU8v07822@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> I do not see a good reason why "fatal" and "off" shouldn't be allowed
> >> values for all three message variables. If we just did that, then you'd
> >> be back to sharable code.
>
> > I recommended he only allow valid values for each variable. I think if
> > we say we only support values X,Y,Z we had better throw an error if it
> > anything else.
>
> That's not what I said: I said allow all the values for each variable.
> And document it. Why shouldn't we let people turn off error logging
> if they want to?
But the client side doesn't make any sense to support FATAL. Am I
missing something?
> > Seems a new GUC variable seems like overkill to me, and I think we need
> > to allow it to be raised. I think we can make server_min_messages
> > PGC_SUSET so only the admin can change it.
>
> Okay, and log_min_error_statement too.
Yes.
--
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 | Tom Lane | 2002-09-05 15:40:35 | Re: I am done |
Previous Message | Dave Page | 2002-09-05 15:30:00 | Re: 7.3 Beta 1 Build Error on Cygwin |