From: Kisung Kim <kskim80@gmail.com>
To: pgsql-bugs@postgresql.org
Subject: Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
Date: Sat, 16 Jan 2021 15:34:17 -0700 (MST)
Message-ID: <1610836457734-0.post@n3.nabble.com> (raw)
In-Reply-To: <1343668.1610583399@sss.pgh.pa.us>
References: <16824-cac06100763db5ae@postgresql.org>
<1343668.1610583399@sss.pgh.pa.us>
Tom Lane-2 wrote
> This is an empirical decision based on the
> frequency with which such a deduction would help versus the planner
> cycles that would be spent looking for such cases.
Is there any thing referring to this decision, like mail threads or
conference materials?
--
Sent from: https://www.postgresql-archive.org/PostgreSQL-bugs-f2117394.html
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 using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: kskim80@gmail.com
Subject: Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
In-Reply-To: <1610836457734-0.post@n3.nabble.com>
* 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