Re: Adding error message "source"
От | Tom Lane |
---|---|
Тема | Re: Adding error message "source" |
Дата | |
Msg-id | 3861.1249570230@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Adding error message "source" (Magnus Hagander <magnus@hagander.net>) |
Список | pgsql-hackers |
Magnus Hagander <magnus@hagander.net> writes: > On Thu, Aug 6, 2009 at 16:33, Tom Lane<tgl@sss.pgh.pa.us> wrote: >> I don't think there'd be much logical difficulty in having an output >> field (ie, CSV column or log_line_prefix escape) that represents a >> classification of the PID, say as "postmaster, backend, AV worker, >> AV launcher, bgwriter, ...". �It would only require changing things >> in one place, whereas your original proposal seemed mighty open-ended. > Good point. That *would* probably take care of much of the need. The > downside is aggressive filtering that way would get rid of important > messages coming out of a single backend, like out of disk space. > Meaning it would still not be possible to filter on the difference > between ERROR: syntax error in query and ERROR: out of disk space? But > it'd be an improvement still. Hmm, well, what about filtering on the SQLSTATE? You could do that today. A category-level filter would probably serve pretty well. regards, tom lane
В списке pgsql-hackers по дате отправления: