On Tue, Mar 10, 2020 at 4:32 AM James Coleman <jtc...@gmail.com> wrote:
> On Mon, Mar 9, 2020 at 3:56 PM Dmitry Dolgov <9erthali...@gmail.com> > wrote: > > > > Assuming we'll implement it in a way that we do not know about what kind > > of path type is that in create_distinct_path, then it can also work for > > ProjectionPath or anything else (if UniqueKeys are present). But then > > still EquivalenceMember are used only to figure out correct > > distinctPrefixKeys and do not affect whether or not skipping is applied. > > What do I miss? > > > Part of the puzzle seems to me to this part of the response: > > > I think the UniqueKeys may need to be changed from using > > EquivalenceClasses to use Exprs instead. > > But I can't say I'm being overly helpful by pointing that out, since I > don't have my head in the code enough to understand how you'd > accomplish that :) > > There was a dedicated thread [1] where David explain his idea very detailed, and you can also check that messages around that message for the context. hope it helps. [1] https://www.postgresql.org/message-id/CAApHDvq7i0%3DO97r4Y1pv68%2BtprVczKsXRsV28rM9H-rVPOfeNQ%40mail.gmail.com
