On Thu, Mar 28, 2019 at 9:48 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>
> On Thu, Mar 28, 2019 at 8:45 AM Sergei Kornilov <sk(at)zsrv(dot)org> wrote:
> >
> > >> Ok, but keep in mind that this is the last commitfest for pg12, and
> > >> there are only 4 days left. Will you have time to take care of it, or
> > >> do you need help on it?
> > >
> > > Oups, sorry, I won't have time nor knowledge to finish in time ;o(
> > > Any help is welcome !
> >
> > No need to rush, this patch has is unlikely to get committed in pg12 even a month earlier. We have a general policy that we don't like complex patches that first show up for the last commitfest of a dev cycle. Current commitfest is last one before feature freeze.
>
> yes, but this patch first showed up years ago:
> https://commitfest.postgresql.org/16/1373/. Since nothing happened
> since, it would be nice to have feedback on whether deeper changes on
> the planning functions are required (so for pg13), or if current
> approach is ok (and then I hope it'd be acceptable for pg12).
If that's helpful I attach the updated patches. I split in two
commits, so if the query_text passing is not wanted it's quite easy to
ignore this part.