Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 0FD50476E52; Wed, 22 Jan 2003 19:35:30 -0500 (EST) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by postgresql.org (Postfix) with ESMTP id D5F5F476026; Wed, 22 Jan 2003 19:17:09 -0500 (EST) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 2322649; Wed, 22 Jan 2003 16:17:16 -0800 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Tom Lane , pgsql-hackers@postgreSQL.org, pgsql-performance@postgreSQL.org Subject: Re: [PERFORM] Proposal: relaxing link between explicit JOINs and execution order Date: Wed, 22 Jan 2003 16:17:41 -0800 X-Mailer: KMail [version 1.4] References: <25071.1043276513@sss.pgh.pa.us> In-Reply-To: <25071.1043276513@sss.pgh.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200301221617.41680.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200301/856 X-Sequence-Number: 34466 Tom, I am very strongly in favor of this idea. I would personally prefer it if= =20 the Join collapsing parmeter could be set at query time through a SET=20 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? --=20 -Josh Berkus Aglio Database Solutions San Francisco