Magnus Hagander <[email protected]> writes:
> On Thu, Aug 6, 2009 at 16:33, Tom Lane<[email protected]> 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
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
