From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-performance@postgreSQL.org
Subject: Re: [PERFORM] Proposal: relaxing link between explicit JOINs and execution order
Date: Wed, 22 Jan 2003 19:21:24 -0500
Message-ID: <25650.1043281284@sss.pgh.pa.us> (raw)
In-Reply-To: <200301221617.41680.josh@agliodbs.com>
References: <25071.1043276513@sss.pgh.pa.us>
<200301221617.41680.josh@agliodbs.com>
Josh Berkus <josh@agliodbs.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, pgsql-hackers@postgreSQL.org
Subject: Re: [PERFORM] Proposal: relaxing link between explicit JOINs and execution order
In-Reply-To: <25650.1043281284@sss.pgh.pa.us>
References: <25071.1043276513@sss.pgh.pa.us> <200301221617.41680.josh@agliodbs.com> <25650.1043281284@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox