Add more clarification about SSH tunnels from Faheem Mitha.

diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml
index b9989d4c859de25c8e6c97a9432f4d6ee3439e63..0e538a09443ba1e7e2be2c6b859a219702feb27d 100644 (file)
--- a/doc/src/sgml/runtime.sgml
+++ b/doc/src/sgml/runtime.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.408 2008/02/26 16:07:16 petere Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.409 2008/02/26 18:01:26 petere Exp $ -->
 
 <chapter Id="runtime">
  <title>Operating System Environment</title>
@@ -1823,6 +1823,10 @@ ssh -L 63333:foo.com:5432 joe@foo.com
 <programlisting>
 ssh -L 63333:db.foo.com:5432 joe@shell.foo.com
 </programlisting>
+   Note that this way the connection
+   from <literal>shell.foo.com</literal>
+   to <literal>db.foo.com</literal> will not be encrypted by the SSH
+   tunnel.
    SSH offers quite a few configuration possibilities when the network
    is restricted in various ways.  Please refer to the SSH
    documentation for details.