From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(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:28:14 |
Message-ID: | 9417.1031239694@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
> 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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Tishler | 2002-09-05 15:29:50 | Re: 7.3 Beta 1 Build Error on Cygwin |
Previous Message | Hannu Krosing | 2002-09-05 15:27:23 | Re: 7.2 - 7.3 activity |