Received: from www.arcamax.com (arcamax.com [209.96.210.66]) by hub.org (8.10.1/8.10.1) with ESMTP id e59FSQT64494 for ; Fri, 9 Jun 2000 11:28:27 -0400 (EDT) Received: from bryan2 (bryan [209.96.210.45]) by www.arcamax.com (8.9.3/8.9.3) with SMTP id LAA01738 for ; Fri, 9 Jun 2000 11:28:26 -0400 Message-ID: <00b701bfd227$58eabec0$2dd260d1@arcamax.com> From: "Bryan White" To: "pgsql-sql" Subject: Client Logging Date: Fri, 9 Jun 2000 11:28:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Archive-Number: 200006/105 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?