Log Message:
-----------
[#1011310] Command timeouts after the first are not handled. Applied patch
[#1011311]. Thank you, Evan Martin, for bug report and patch!
When a command inside a transaction times out the caller may roll back to a
savepoint and try again. This works OK the first time. The second time it
appears to work, but the rollback takes a long time. On the third attempt the
command returns an empty result set. The attached console app reproduces the
problem. On investigation, it appears that Npgsql is not cancelling any command
after the first, once NpgsqlConnector.CancelRequestCalled is true.
Modified Files:
--------------
Npgsql2/src/Npgsql:
NpgsqlConnector.cs (r1.39 -> r1.40)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlConnector.cs?r1=1.39&r2=1.40)
NpgsqlReadyState.cs (r1.6 -> r1.7)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlReadyState.cs?r1=1.6&r2=1.7)
NpgsqlState.cs (r1.24 -> r1.25)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlState.cs?r1=1.24&r2=1.25)
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
