From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Chris Angelico <rosuav(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to print application_name in log_line_prefix (using %a)? |
Date: | 2012-10-29 16:08:46 |
Message-ID: | CAMkU=1wzDw324kcKog14=ktGxoJaWzhKpqu3vxcLsHw9L4Ssnw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Oct 29, 2012 at 8:58 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Chris Angelico <rosuav(at)gmail(dot)com> writes:
>> On Mon, Oct 29, 2012 at 5:44 PM, Tianyin Xu <tixu(at)cs(dot)ucsd(dot)edu> wrote:
>>> I still wonder why application_name appears in the configuration file if it
>>> cannot take effort :-P
>
>> Not sure what you mean by that, but my postgresql.conf doesn't have
>> anything about application_name. But if it did, it would be a default
>> that an application can override.
>
> The reason background processes don't print anything for %a is that it's
> presumed it couldn't possibly be set to anything meaningful.
Why wouldn't 'bgwriter', 'autovacuum', 'checkpointer', etc. be meaningful?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2012-10-29 16:12:50 | Re: Why BgWriterDelay is fixed? |
Previous Message | Jeff Janes | 2012-10-29 16:00:53 | Re: Access to postgresql query optimizer output |