From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: process type escape for log_line_prefix |
Date: | 2016-02-10 05:39:32 |
Message-ID: | CAB7nPqS=wBbZzBcty1KyN-5Y9bPXZ+deJbfcCtebf06eF2Uyvg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 8, 2016 at 11:32 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> Frequently when reading postgres logs to do some post mortem analysis
> I'm left wondering what process emitted an error/log message. After the
> fact it's often hard to know wether an error message was emitted by a
> user backend or by something internal, say the checkpointer or
> autovacuum. Logging all process starts is often impractical given the
> log volume that causes.
>
> So I'm proposing adding an escape displaying the process title (say 'k'
> for kind?). So %k would emit something like "autovacuum worker process",
> "wal sender process" etc.
It would be nice to get something consistent between the ps output and
this new prefix, say with for example a miscadmin.h parameter like
MyProcName.
> I'm thinking it might make sense to give normal connections "" as the
> name, they're usually already discernible.
Yeah, that sounds fine for me. What about background workers? I would
think that they should use BackgroundWorker->bgw_name.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2016-02-10 05:44:04 | pgcrypto: add s2k-count |
Previous Message | Michael Paquier | 2016-02-10 05:06:54 | Re: Bug in StartupSUBTRANS |