From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Subject: | Re: Adding error message "source" |
Date: | 2009-08-10 13:14:49 |
Message-ID: | 9837222c0908100614k3009fdf1y250e90bc7dfa2273@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 6, 2009 at 19:04, Peter Eisentraut<peter_e(at)gmx(dot)net> wrote:
> On Thursday 06 August 2009 17:33:40 Tom Lane 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.
>
> You might be able to achieve that if you use the %q escape and put something
> after the %q that you can search for.
You could do part of it, but you could still not differ them from each
other. And really, it seems very much like a kludge to me. I'd rather
have a "proper field" for it.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2009-08-10 13:17:04 | Re: Alpha releases: How to tag |
Previous Message | Andrew Dunstan | 2009-08-10 13:00:45 | Re: machine-readable explain output v4 |