pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kisung Kim <kskim80@gmail.com>
Cc: pgsql-bugs@postgresql.org
Subject: Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
Date: Sat, 16 Jan 2021 18:28:23 -0500
Message-ID: <106470.1610839703@sss.pgh.pa.us> (raw)
In-Reply-To: <1610836457734-0.post@n3.nabble.com>
References: <16824-cac06100763db5ae@postgresql.org>
	<1343668.1610583399@sss.pgh.pa.us>
	<1610836457734-0.post@n3.nabble.com>

Kisung Kim <kskim80@gmail.com> writes:
> 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?

[ shrug... ]  It's doubtless been discussed on pgsql-hackers in the past,
but I don't plan to go digging through those archives for you.  Looking
for constraint exclusion via

https://www.postgresql.org/search/?m=1

or your favorite search engine might help you.

			regards, tom lane





view thread (4+ messages)

Message-ID: <106470.1610839703@sss.pgh.pa.us>
Permalink:  ../106470.1610839703@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/106470.1610839703@sss.pgh.pa.us

 · 

reply

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: tgl@sss.pgh.pa.us, kskim80@gmail.com
  Subject: Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
  In-Reply-To: <106470.1610839703@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