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 identi
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 esta
