DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Sd+AwLmS/DrRJCR9gMHYldjQyCHPHwtwJihIExzVpY3aIpAPAoHMZ/CnweHLU9Ecek41TcKQ59XXNH8bEDurlZpwGUpWFDobjHrmRKkhmC/HVUQsasoUWwImVMlrOV5oW9ae5f4xih9oYgStlBjEieX4jgPHP3GCQu0LUed3aLg=
Message-ID: <758d5e7f050718005164cbe9a4@mail.gmail.com>
Date: Mon, 18 Jul 2005 09:51:41 +0200
From: Dawid Kuroczko <qnex42@gmail.com>
Reply-To: Dawid Kuroczko <qnex42@gmail.com>
To: Bruno Wolff III <bruno@wolff.to>,
	Dan Harris <fbsd@drivefaster.net>, pgsql-performance@postgresql.org
Subject: Re: slow joining very large table to smaller ones
In-Reply-To: <20050715164458.GA26178@wolff.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <46AF8F35-B735-4DFA-BA0A-AC82B5DA3CCE@drivefaster.net>
	<42D687E5.7080202@arbash-meinel.com>
	<C3470621-9DB0-444A-BAD1-F9995E0142FB@drivefaster.net>
	<20050715164458.GA26178@wolff.to>

On 7/15/05, Bruno Wolff III <bruno@wolff.to> wrote:
> On Thu, Jul 14, 2005 at 16:29:58 -0600,
>   Dan Harris <fbsd@drivefaster.net> wrote:
> >
> > Ok, I tried this one.  My ssh keeps getting cut off by a router
> > somewhere between me and the server due to inactivity timeouts, so
> > all I know is that both the select and explain analyze are taking
> > over an hour to run.  Here's the explain select for that one, since
> > that's the best I can get.
>=20
> Are you using NAT at home? That's probably where the issue is. If you
> have control of that box you can probably increase the timeout to a
> couple of hours.

Some versions of ssh have such a configuration option (in .ssh/config):

Host *
        ServerAliveInterval 600

...it means that ssh will send a "ping" packet to a sshd every 10 minutes
of inactivity.  This way NAT will see activity and won't kill the session.
I'm using OpenSSH_4.1p1 for this...

Oh, and it doesn't have anything to do with TCP keep alive, which is
rather for finding dead connections than keeping connections alive. ;)

   Regards,
       Dawid