Re: quieting DEBUG3
| От | Christopher Browne |
|---|---|
| Тема | Re: quieting DEBUG3 |
| Дата | |
| Msg-id | CAFNqd5V0nu588A=1j9d0xY6Py-jdZRQcMExvjwN-Rot=YjvBDQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: quieting DEBUG3 (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
On 27 October 2015 at 20:51, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Craig Ringer <craig@2ndquadrant.com> writes:
> > I think it'd be helpful to define some level of policy about what the
> > debug levels are intended for, so there's some guidance on what level
> > to emit messages on rather than playing "pick a number".
>
> +1 ... I doubt anyone has ever looked at that in a holistic way.
>
> regards, tom lane
A few years ago, I went through Slony's logging with a view to this very thing.
It was pretty fruitful in changing log levels for a lot of things, and actually>
> Craig Ringer <craig@2ndquadrant.com> writes:
> > I think it'd be helpful to define some level of policy about what the
> > debug levels are intended for, so there's some guidance on what level
> > to emit messages on rather than playing "pick a number".
>
> +1 ... I doubt anyone has ever looked at that in a holistic way.
>
> regards, tom lane
A few years ago, I went through Slony's logging with a view to this very thing.
Looking through the Postgres code base to this end seems likely to be
pretty useful, and I agree, it would need to be done holisticly.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
В списке pgsql-hackers по дате отправления: