public inbox for [email protected]
help / color / mirror / Atom feedFrom: Winner Lohas <[email protected]>
To: [email protected]
Subject: Does ODBC driver connection pooling have a bug?
Date: Wed, 13 Mar 2024 05:04:35 +0900
Message-ID: <CAED_kjmh0qyCnPwmOg5f285uH8bDahPg42sHDu=vqOWmzKyH6w@mail.gmail.com> (raw)
Hello.
I was using the ODBC driver and found that the problem occurred in a
temporary table.
However, when I worked with C# with Npgsql (PostgreSQL .NET driver), there
were no problems even though connection pooling was working. When a
connection is reused internally, DISCARD ALL is done first. So the
temporary table is also automatically dropped.
I also tested MySQL, and the MySQL ODBC driver worked without problem.
However, looking at the network protocol, it seems like the authentication
process is almost done again rather than a connection reset. The process
took quite a long time because it seemed that only the TCP connection was
being reused rather than FIN. What's interesting is that the ODBC data
source manager is installed with pooling turned off by default.
The default setting of MS SQL Server's ODBC driver is to use pooling, and
it works well with or without pooling. Internally, sp_reset_connection is
executed to initialize reused connections.
Regards.
Wooseung Kim
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Does ODBC driver connection pooling have a bug?
In-Reply-To: <CAED_kjmh0qyCnPwmOg5f285uH8bDahPg42sHDu=vqOWmzKyH6w@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox