> On 4 Jul 2023, at 14:02, David Rowley wrote:
> I'm going to mark this as waiting on author in the CF app. It might be
> better if you withdraw it and resubmit when you have a patch that
> addresses the worst-case regression issue.
Since there hasn't been any updates to this thread I am marking
On Thu, 13 Apr 2023 at 03:00, Alexandr Nikulin
wrote:
> explain analyze select * from ids join test_part on ids.id=test_part.id where
> ascii(ids.name)=ascii('best case');
> explain analyze select * from ids join test_part on ids.id=test_part.id where
> ascii(ids.name)=ascii('worst case');
>
> T
05, David Rowley :
> On Thu, 23 Mar 2023 at 19:46, Alexandr Nikulin
> wrote:
> > I propose to slightly improve the performance of nested loop join in the
> case of partitioned inner table.
> > As I see in the code, the backend looks for the partition of the inner
> table ea
On Thu, 23 Mar 2023 at 19:46, Alexandr Nikulin
wrote:
> I propose to slightly improve the performance of nested loop join in the case
> of partitioned inner table.
> As I see in the code, the backend looks for the partition of the inner table
> each time after fetch a new row fr
Hi, hackers
I propose to slightly improve the performance of nested loop join in the
case of partitioned inner table.
As I see in the code, the backend looks for the partition of the inner
table each time after fetch a new row from the outer table.
These searches can take a significant amount of
