Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C1882476E89; Wed, 22 Jan 2003 19:38:08 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id E3970476F45; Wed, 22 Jan 2003 19:21:43 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h0N0LO5u025651; Wed, 22 Jan 2003 19:21:24 -0500 (EST) To: josh@agliodbs.com Cc: pgsql-hackers@postgreSQL.org, pgsql-performance@postgreSQL.org Subject: Re: [PERFORM] Proposal: relaxing link between explicit JOINs and execution order In-reply-to: <200301221617.41680.josh@agliodbs.com> References: <25071.1043276513@sss.pgh.pa.us> <200301221617.41680.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Wed, 22 Jan 2003 16:17:41 -0800" Date: Wed, 22 Jan 2003 19:21:24 -0500 Message-ID: <25650.1043281284@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/859 X-Sequence-Number: 34469 Josh Berkus writes: > 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. I guess I failed to make it clear that that's what I meant. GUC variables are those things that you can set via SET, or in the postgresql.conf file, etc. These values would be just as manipulable as, say, ENABLE_SEQSCAN. > How about: > EXPLICIT_JOIN_MINIMUM > and > FROM_COLLAPSE_LIMIT > Just to make the two params not sound so identical? Hmm. The two parameters would have closely related functions, so I'd sort of think that the names *should* be pretty similar. regards, tom lane