From: Marko Kreen <markokr@gmail.com>
Date: Mon, 19 Nov 2007 09:57:16 +0000 (+0000)
Subject: remove more mentions of statement_timeout
X-Git-Tag: plproxy_2_0_3rc1~1
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=c8e774f8ae10bf6ec4c67f36c71e6b26ef388da9;p=plproxy.git

remove more mentions of statement_timeout
---

diff --git a/doc/config.txt b/doc/config.txt
index 9009a7e..926c9ba 100644
--- a/doc/config.txt
+++ b/doc/config.txt
@@ -59,8 +59,8 @@ Timeouts/lifetime are given in seconds. If 0 or NULL then disabled.
   query_timeout::
 
 	If query result does not appear in this time, the connection
-	is closed.  If set then also statement_timeout should be set
-	and to somewhat smaller value, so it takes effect earlier.
+	is closed.  If set then also `statement_timeout` should be set
+	remotely to somewhat smaller value, so it takes effect earlier.
 	It is meant for surviving network problems, not long queries.
 
   disable_binary::
diff --git a/sql/plproxy_init.sql b/sql/plproxy_init.sql
index 19d444f..280eb7c 100644
--- a/sql/plproxy_init.sql
+++ b/sql/plproxy_init.sql
@@ -29,9 +29,6 @@ create or replace function
 plproxy.get_cluster_config(cluster_name text, out key text, out val text)
 returns setof record as $$
 begin
-    key := 'statement_timeout';
-    val := 0;
-    return next;
     return;
 end; $$ language plpgsql;