pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Client Logging
2+ messages / 2 participants
[nested] [flat]

* Client Logging
@ 2000-06-09 15:28 Bryan White <bryan@arcamax.com>
  2000-06-11 11:45 ` Re: Client Logging Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 1 reply; 2+ messages in thread

From: Bryan White @ 2000-06-09 15:28 UTC (permalink / raw)
  To: pgsql-sql

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?




^ permalink  raw  reply  [nested|flat] 2+ messages in thread

* Re: Client Logging
  2000-06-09 15:28 Client Logging Bryan White <bryan@arcamax.com>
@ 2000-06-11 11:45 ` Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 0 replies; 2+ messages in thread

From: Peter Eisentraut @ 2000-06-11 11:45 UTC (permalink / raw)
  To: Bryan White <bryan@arcamax.com>; +Cc: pgsql-sql

Bryan White writes:

> I sometimes need to be able to identify what client application is
> causing messages that are appering in the backend log file.

I've been thinking about that too a while ago, but it depends on whether
you want to do this for auditing purposes, in which case

> 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.

is not reliable. If you want to have this on a cooperative basis, then

> 3) A function that takes a string argument and calls elog.

is probably reasonable.


-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden




^ permalink  raw  reply  [nested|flat] 2+ messages in thread


end of thread, other threads:[~2000-06-11 11:45 UTC | newest]

Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-06-09 15:28 Client Logging Bryan White <bryan@arcamax.com>
2000-06-11 11:45 ` Peter Eisentraut <peter_e@gmx.net>

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