Re: Simple join optimized badly? - Mailing list pgsql-performance

From Bruno Wolff III
Subject Re: Simple join optimized badly?
Date
Msg-id 20061010164534.GA11843@wolff.to
Whole thread Raw
In response to Re: Simple join optimized badly?  (Tobias Brox <tobias@nordicbet.com>)
List pgsql-performance
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.

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: long running transactions
Next
From: Tobias Brox
Date:
Subject: Re: long running transactions