You should be able to trace from ODBC, but, regardless of how the
control panel applet appears, you must close the applet after starting
the log in order for the log to be generated. Then you have to reopen
the applet to stop the log. Pretty crummy, eh? I have done this when a
query I was running from Access was failing.
Hope this helps.
Chris Gamache wrote:
>PgODBC's logfiles don't have a time index, and you also can't change the output
>location of the files unless you recompile the driver (unless you know
>something that I don't). My C drive is strictly OS, and there's not much
>breathing room there. I can't get PgODBC to build under VisualStudio.NET, so a
>recompile to include timestamp and variable logfile location is out of my
>ability. I don't know why, but I can not get a trace from the ODBC control
>panel either. Can you help?
>--- Richard Huxton <dev(at)archonet(dot)com> wrote:
>>On Wednesday 31 March 2004 15:24, Chris Gamache wrote:
>>>Some of my ODBC connections are dying unexpectedly (and randomly) with the
>>>Postgresql Log Message "unexpected EOF on client connection" ... It happens
>>>about one in every 50K-100K queries.
>>This is commonly the client crashing / timing out.
>>>I would really appreciate some suggestions for a method to find the cause
>>>of these dropped connections.
>>You could turn logging on at the client end - there are settings in the odbc
>>driver settings. Could be a big log-file though, if you have to wait 100,000
>> Richard Huxton
>> Archonet Ltd
>Do you Yahoo!?
>Yahoo! Small Business $15K Web Design Giveaway
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
In response to
pgsql-odbc by date
|Next:||From: scott.marlowe||Date: 2004-04-01 20:57:44|
|Subject: Re: stored procedures with parameters w/dotnet|
|Previous:||From: Richard Huxton||Date: 2004-04-01 20:18:17|
|Subject: Re: Troubleshoot "unexpected EOF on client connection"|