From: Bruno Wolff III <bruno@wolff.to>
To: Tobias Brox <tobias@nordicbet.com>
Cc: Jim C. Nasby <jim@nasby.net>
Cc: Chris Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: Simple join optimized badly?
Date: Tue, 10 Oct 2006 11:45:34 -0500
Message-ID: <20061010164534.GA11843@wolff.to> (raw)
In-Reply-To: <20061009213303.GA19144@oppetid.no>
References: <20061009213303.GA19144@oppetid.no>
On Mon, Oct 09, 2006 at 23:33:03 +0200,
Tobias Brox <tobias@nordicbet.com> wrote:
>
> Just a comment from the side line; can't the rough "set
> enable_seqscan=off" be considered as sort of a hint anyway? There have
> been situations where we've actually had to resort to such crud.
That only works for simple queries. To be generally useful, you want to
be able to hint how to handle each join being done in the query. The
current controlls affect all joins.
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: bruno@wolff.to, tobias@nordicbet.com, jim@nasby.net, cbbrowne@acm.org
Subject: Re: Simple join optimized badly?
In-Reply-To: <20061010164534.GA11843@wolff.to>
* 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