From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | MauMau <maumau307(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Feature proposal: distinguish each PostgreSQL instance in the event log |
Date: | 2011-05-11 07:58:21 |
Message-ID: | BANLkTikQp9kzrL_E-LpP=e8-vve+b6B_Rw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 10, 2011 at 11:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "MauMau" <maumau307(at)gmail(dot)com> writes:
>>> "MauMau" <maumau307(at)gmail(dot)com> writes:
>>>> I've encountered one problem on Windows. I need to support running all of
>>>> my
>>>> products on one host simultaneously. Plus, I need to log messages in
>>>> syslog/event log. On Linux, I can distinguish the messages of one product
>>>> and those of other products by setting syslog_ident in postgresql.conf.
>>>> On
>>>> the other hand, I can't do that on Windows: all of the PostgreSQL
>>>> instances
>>>> use the same fixed event source name "PostgreSQL".
>
>>>> SO I'd like to propose a trivial feature which allows users to set event
>>>> source.
>
> BTW, what will this accomplish exactly that couldn't be accomplished by
> setting log_line_prefix to include the desired identifier?
Windows uses the event source field to show where events in the logs
have come from. The Event Viewer and other network management tools
expect to be able to use the field for sorting and filtering etc, so
having a different value for different PG instances allows those tools
to distinguish between them properly. It's also useful for ISVs who
may want to make an embedded PG instance used by their apps identify
itself differently from other instances.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Shigeru Hanada | 2011-05-11 07:59:11 | Re: Foreign table permissions and cloning |
Previous Message | Simon Riggs | 2011-05-11 07:17:37 | Re: the big picture for index-only scans |