| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| 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-05 01:28:23 |
| Message-ID: | 41118D37.4050802@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> If I want the planner/optimizer to always choose merge join when it needs to
> join relations. How can I do it ?
You can't, unless in your transaction you set enable_nestloop,
enable_seqscan, etc. all to off except for the join type you want.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2004-08-05 01:30:57 | Re: query result set caching |
| Previous Message | Duane Lee - EGOVX | 2004-08-05 00:52:56 | Re: most idiomatic way to "update or insert"? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-08-05 01:32:42 | Re: enforcing a join type |
| Previous Message | Dave Cramer | 2004-08-05 01:22:59 | Re: [HACKERS] postgres and Jdbc 2.0 |