views:

1400

answers:

4

I am using PostgreSQL in a project I am working on, and one of the queries is timing out. I need to increase the timeout on the database connection, but since I am using my DAO through a complex wrapper to Active Record and NHibernate, I am not able to adjust the timeout of the command object - so I am hoping you can change the timeout through the connection string.

Any ideas?

+2  A: 

Try this one:

Provider=PostgreSQL OLE DB Provider;Data Source=myServerAddress;location=myDataBase;User ID=myUsername;password=myPassword;timeout=1000;

Just replace the obvious parts (myUsername, myServerAddress, etc...) with your stuff.

Also, for your reference, this site will give you connection string templates for pretty much any database on earth for pretty much any way you need to use it:

http://www.connectionstrings.com

EdgarVerona
+1  A: 

Have you tried to optimize the query? Optimizing is the best choice over increasing timeouts.

RedWolves
I second this, explain analyse is your friend. Look for slow sequential scans and a poor join order, etc.
Dana the Sane
A: 

Npgsql-native connection string:

Server=127.0.0.1;Port=5432;Userid=u;Password=p;Protocol=3;SSL=false;Pooling=false;MinPoolSize=1;MaxPoolSize=20;Timeout=15;SslMode=Disable;Database=test"
Michael Buen
A: 

Found it: CommandTimeout=20;Timeout=15;

Ash