Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kisung Kim <kskim80(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination
Date: 2021-01-16 23:28:23
Message-ID: 106470.1610839703@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Kisung Kim <kskim80(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-01-17 02:18:42 Re: syntactically correct query gives ERROR: failed to assign all NestLoopParams to plan nodes
Previous Message Kisung Kim 2021-01-16 22:34:17 Re: BUG #16824: Planner chooses poor path on query with Merge Join and pagination