On Mon, Jul 10, 2023 at 5:27 PM Daniel Gustafsson <daniel@yesql.se> wrote:
> > On 21 Mar 2023, at 06:03, Amit Langote <amitlangote09@gmail.com> wrote:
> > On Tue, Mar 21, 2023 at 3:54 AM Gregory Stark (as CFM) <stark.cfm@gmail.com> wrote:
> >> On Mon, 17 Oct 2022 at 14:59, Robert Haas <robertmhaas@gmail.com> wrote:
>
> >>> But I think the bigger problem for this patch set is that the
> >>> design-level feedback from
> >>>
https://www.postgresql.org/message-id/CA%2BTgmoaiTNj4DgQy42OT9JmTTP1NWcMV%2Bke0i%3D%2Ba7%3DVgnzqGXw%40mail.gmail.com
> >>> hasn't really been addressed, AFAICS. ri_LookupKeyInPkRelPlanIsValid
> >>> is still trivial in v7, and that still seems wrong to me. And I still
> >>> don't know how we're going to avoid changing the semantics in ways
> >>> that are undesirable, or even knowing precisely what we did change. If
> >>> we don't have answers to those questions, then I suspect that this
> >>> patch set isn't going anywhere.
> >>
> >> Amit, do you plan to work on this patch for this commitfest (and
> >> therefore this release?). And do you think it has a realistic chance
> >> of being ready for commit this month?
> >
> > Unfortunately, I don't think so.
>
> This thread has stalled with the patch not building and/or applying for a
> while, so I am going to mark this Returned with Feebdback.
Agreed, I was about to do so myself.
I'll give this another try later in the cycle.
--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com
