| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | process type escape for log_line_prefix |
| Date: | 2016-02-08 14:32:31 |
| Message-ID: | 20160208143231.tqf6ydt5ohnosozn@alap3.anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
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.
I'm thinking it might make sense to give normal connections "" as the
name, they're usually already discernible.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2016-02-08 14:36:40 | Re: remove wal_level archive |
| Previous Message | Amit Kapila | 2016-02-08 14:24:31 | Re: Re: BUG #13685: Archiving while idle every archive_timeout with wal_level hot_standby |