On Tue, May 10, 2011 at 11:55 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > "MauMau" <maumau...@gmail.com> writes: >>> "MauMau" <maumau...@gmail.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
