Just wanted to let you know that making this more flexible would be a great help in driver implementation. Npgsql maintains its own view of the current statement_timeout parameter for various reasons; as long as the standard ADO.NET API is used to change the timeout everything is OK, but if the user ever manually sets statement_timeout things can become quite messy. Being able to subscribe to more parameter changes would help in this case. In the very short term simply adding statement_timeout to the hard-wired set would help me as well.