On Tue, Jan 28, 2025 at 5:30 PM Felipe López Montes <xoca...@gmail.com> wrote:
> For the sake of clarity and simplicity, I have disabled the nestloop join > in the session because it involved a gather clause and parallel workers and > was still underestimating rows, so the same problem happens with nestloop > strategy too. Instead now the planner goes for a merge join ( if you still > prefer me to send you the nestloop plan, I can do): > Yes, please, send the exact plan you are having problems with. Also, what exactly is the performance issue? It seems your *second best plan* is running in 36 milliseconds? Cheers, Greg P.S. In the future, you can use this to quickly grab relevant settings: select name, current_setting(name) from pg_settings where source <> 'default';
