| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org, pgsql-performance(at)postgreSQL(dot)org |
| Subject: | Re: [PERFORM] Proposal: relaxing link between explicit JOINs and execution order |
| Date: | 2003-01-23 00:17:41 |
| Message-ID: | 200301221617.41680.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Tom,
I am very strongly in favor of this idea. I would personally prefer it if
the Join collapsing parmeter could be set at query time through a SET
statement, but will of course defer to the difficulty level in doing so.
> Comments? In particular, can anyone think of pithy names for these
> variables? The best I'd been able to come up with is MAX_JOIN_COLLAPSE
> and MAX_FROM_COLLAPSE, but neither of these exactly sing...
How about:
EXPLICIT_JOIN_MINIMUM
and
FROM_COLLAPSE_LIMIT
Just to make the two params not sound so identical?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-01-23 00:18:07 | Re: Terrible performance on wide selects |
| Previous Message | Dann Corbit | 2003-01-23 00:06:26 | Re: Terrible performance on wide selects |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-01-23 00:18:07 | Re: Terrible performance on wide selects |
| Previous Message | Dann Corbit | 2003-01-23 00:06:26 | Re: Terrible performance on wide selects |