Hi, On Wed, Jun 7, 2023 at 7:28 PM Nishant Sharma <nishant.sha...@enterprisedb.com> wrote: > Etsuro's patch is also showing the correct output for "set > enable_nestloop=off". Looks good to me for back branches due to backport > issues. > > But below are a few observations for the same:- > 1) I looked into the query plan for both "set enable_nestloop" on & off case > and observe that they are the same. That is, what we see with "set > enable_nestloop=on". > 2) In back branches for "set enable_nestloop" on & off value, at least this > type of query execution won't make any difference. No comparison of plans to > be selected based on total cost of two plans old (Nested Loop with Foreign > Scans) & new (Only Foreign Scan) will be done, because we are avoiding the > call to "postgresGetForeignJoinPaths()" up front when we have pseudo > constants.
Thanks for looking! Best regards, Etsuro Fujita
