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
