-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
On Mon, 24 Jan 2005, Tom Lane wrote:
I've changed statement_timeout value from 5 to 0; restarted PostgreSQL and all commands are running now... So, what could be the problem with statement_timeout?
Apparently you need a timeout longer than 5 milliseconds.
Note that the first few queries executed by a backend will take longer than "usual" because of the overhead of populating the catalog caches.
What I'm confused was "miliseconds", I saw it as "seconds" :)
Anyway, thanks.
- --
Devrim GUNDUZ devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFB9SYgtl86P3SPfQ4RAiAIAJ9aXeD9lTZKQKpjKdtvmp+Mczi16ACeNbYW jtBVhUuI18xw8pF7RGKR1sE= =iuHJ -----END PGP SIGNATURE-----
---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
