Hello! Tell me please. I have the following situation:
Is this considered normal behavior of a synchronous ExecuteReader?
In my scenario, I cannot use the asynchronous API (a lot of legacy code), so my task is to reverse the synchronous operation without waiting for the Command Timeout.
I will be glad to hear advice on which direction to move to solve the problem.
NpgsqlCommand.Cancelwhich will open a new connection and send a request to stop the current command running on the first connection.