From: | "Scott Marlowe" <smarlowe(at)qwest(dot)net> |
---|---|
To: | "Hicham G(dot) Elmongui" <elmongui(at)cs(dot)purdue(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: enforcing a join type |
Date: | 2004-08-04 22:41:10 |
Message-ID: | 1091659270.27166.146.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Wed, 2004-08-04 at 14:53, Hicham G. Elmongui wrote:
> Hi,
> If I want the planner/optimizer to always choose merge join when it needs to
> join relations. How can I do it ?
>From my past experience, I'd guess what you're really trying to do is
STOP the planner from choosing a nested_loop join, in which case it's
quite easy:
set enable_nestloop = off;
select * from ...
Of course, you could apply the same basic trick to all other join
methods, and postgresql would then favor using the merge join.
From | Date | Subject | |
---|---|---|---|
Next Message | Oscar Tuscon | 2004-08-04 23:20:18 | Sequence question |
Previous Message | Jerry LeVan | 2004-08-04 21:06:11 | Re: Simplfied Bytea input/output? |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2004-08-04 22:45:19 | Re: [HACKERS] compile warnings |
Previous Message | Oliver Jowett | 2004-08-04 22:39:07 | making integer_datetimes report on startup |