From: Bryan White <bryan@arcamax.com>
To: pgsql-sql <pgsql-sql@postgreSQL.org>
Subject: Client Logging
Date: Fri, 9 Jun 2000 11:28:22 -0400
Message-ID: <00b701bfd227$58eabec0$2dd260d1@arcamax.com> (raw)
I sometimes need to be able to identify what client application is causing
messages that are appering in the backend log file. To do this I want the
client to identify itself in the log file.
I can see 3 ways this could be implemented:
1) An identification string passed when a connection is established. This
string would either be immediatly logged or included in the log entry for
any subsequent messages for that connection.
2) A sql statement to print to the log file.
3) A function that takes a string argument and calls elog.
#1 would be ideal but requires digging into the source code. #2 seams wrong
headed. I can implement #3 locally myself.
Before I go any farther, has something like this already been invented?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: bryan@arcamax.com
Subject: Re: Client Logging
In-Reply-To: <00b701bfd227$58eabec0$2dd260d1@arcamax.com>
References: <00b701bfd227$58eabec0$2dd260d1@arcamax.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox