From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Adding error message "source" |
Date: | 2009-08-06 14:33:40 |
Message-ID: | 3555.1249569220@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Aug 6, 2009 at 16:20, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-06 14:36:58 | Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables |
Previous Message | Andrew Dunstan | 2009-08-06 14:32:46 | Re: Re: [Pg-migrator-general] Composite types break pg_migratedtables |