From: Dawid Kuroczko <qnex42@gmail.com>
To: Bruno Wolff III <bruno@wolff.to>
To: Dan Harris <fbsd@drivefaster.net>
To: pgsql-performance@postgresql.org
Subject: Re: slow joining very large table to smaller ones
Date: Mon, 18 Jul 2005 09:51:41 +0200
Message-ID: <758d5e7f050718005164cbe9a4@mail.gmail.com> (raw)
In-Reply-To: <20050715164458.GA26178@wolff.to>
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.
>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: qnex42@gmail.com, bruno@wolff.to, fbsd@drivefaster.net
Subject: Re: slow joining very large table to smaller ones
In-Reply-To: <758d5e7f050718005164cbe9a4@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox