Message-ID: <gh-pgjdbc-pgjdbc-3511-c2917509682@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 28 May 2025 20:20:10 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3511: Performance Regression in JDBC Driver 42.7.5 - getCrossReference
In-Reply-To: <gh-pgjdbc-pgjdbc-3511@github.com>
References: <gh-pgjdbc-pgjdbc-3511@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 2917509682
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3511
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3511#issuecomment-2917509682
Content-Type: text/plain; charset=utf-8

It is strange adding the filter impacts the plan in such a way, however, it looks like I've made the same change in https://github.com/pgjdbc/pgjdbc/pull/3641, and I get 40ms->4ms boost on my machine.