Re: Updating psql for features of new FE/BE protocol

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: Kevin Brown <kevin(at)sysexperts(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Updating psql for features of new FE/BE protocol
Date: 2003-06-26 00:54:48
Message-ID: 200306260054.h5Q0smI18238@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> > Tom Lane wrote:
> >> Also, I would like to provide the same set of options w.r.t. messages
> >> logged in the server log. Here there is an additional frammish that
> >> could be imagined, ie, more detail for more-serious errors. Any
> >> opinions about what it should look like?
>
> > Not sure exactly what you're asking for here. If you're asking what
> > additional detail should be included for more serious errors,
>
> No, I was asking whether anyone thought such behavior should be
> user-controllable, and if so exactly how the controlling GUC variables
> should be defined.
>
> One way I could imagine doing it is to split log_min_messages into
> three variables, along the lines of "minimum message level to produce
> a TERSE report", "minimum message level to produce a DEFAULT report",
> and "minimum message level to produce a VERBOSE report". This seems
> a bit inelegant though. Better ideas anyone?

I doubt someone would want to control terse/default/verbose at various
levels --- I assume they would just want all their messages to be
terse/default/ or verbose.

--
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John DeSoi 2003-06-26 01:09:30 row description for domain in 7.4
Previous Message The Hermit Hacker 2003-06-26 00:47:41 Re: Two weeks to feature freeze