Magnus Hagander <mag...@hagander.net> writes:
> On Thu, Aug 6, 2009 at 16:20, Tom Lane<t...@sss.pgh.pa.us> wrote:
>> Well, it seems like you could get 90% of the way there just by filtering
>> on the PID --- watching the bgwriter, walwriter, and archiver should
>> cover this use-case reasonably well.
> Right. But that's pretty hard to do automated, since they will get a
> new pid whenever the database is restarted. Which is hopefully not
> very often, but still an issue. Plus, it's hard to do any kind of
> historical look at things.
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.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
