Re: Adding error message "source"

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Subject: Re: Adding error message "source"
Date: 2009-08-06 17:04:04
Message-ID: 200908062004.04711.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-08-06 17:16:46 Re: the case for machine-readable error fields
Previous Message Peter Eisentraut 2009-08-06 17:02:30 Null handling and plpython