From: sergey-krasnogorov (@sergey-krasnogorov) <noreply+sergey-krasnogorov@github.com>
To: postgresql-interfaces/psqlodbc <noreply+postgresql-interfaces-psqlodbc@github.com>
Subject: Re: [postgresql-interfaces/psqlodbc] issue #224: psqlODBC driver or MS System.Data.Odbc do not report connection lost
Date: Thu, 29 Oct 2026 14:28:02 +0000
Message-ID: <gh-postgresql-interfaces-psqlodbc-224-c6499402889@github.com> (raw)
In-Reply-To: <gh-postgresql-interfaces-psqlodbc-224@github.com>
References: <gh-postgresql-interfaces-psqlodbc-224@github.com>
Thank you for reply Dave,
Answering your questions:
Connection pooling is enabled for the driver, set to 60s.
Client app is built against .NET 4.7.2.
Connection string is widely shared in attached logs I think.
Yes, app does share one OdbcConnection across threads but uses custom in-house implemented concurrency handling mechanism. Moreover, 'connection lost' errors occurred right after service startup/is_ready/connect, on first/second/third SELECT depending on how happy we are.
Attached are logs we were able to collect for Scenario #2 (connection lost), but they don't tell us much. What else should be specifically configured for logging to get information we want to see there?
I "updated" postgresql-2026-10-28_170320.log by inserting part of app log there. Seems like the server was unresponsive at that time (?)
[#224_logs_01.zip](https://github.com/user-attachments/files/34137155/224_logs_01.zip)
Best regards,
Sergey Krasnogorov