Message-ID: <gh-pgjdbc-pgjdbc-3166-c2012490524@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 21 Mar 2024 14:45:04 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3166: query_id in pg_stat_activity is NULL when connecting from JDBC, but not from psql
In-Reply-To: <gh-pgjdbc-pgjdbc-3166@github.com>
References: <gh-pgjdbc-pgjdbc-3166@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: davecramer
X-GitHub-Comment-Id: 2012490524
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3166
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3166#issuecomment-2012490524
Content-Type: text/plain; charset=utf-8

> I can verify that `preferQueryMode=simple` does change the behavior (`query_id` now has a value) Then: **why** isn't `simple` the _default_ (**probably** for some other good reason: like _performance_ or _something else_)

To avoid SQL injection
> 
> If I should go ahead and change the jdbc URL for _all_ involved client (appservers/and-various-tools), which is doable but not really the **preferred way** Is there anyway to _force_ the changes on the server side?

No
> 
> I would still **question** why `query_id` is NULL in `pg_stat_activity` even when the default setting for `preferQueryMode=extended` When I investigate even further I can see that `queryid` in `pg_stat_statements` **does** have a value... (so the calculation _seems_ to happen, but not just for `pg_stat_activity`)

see https://postgrespro.com/list/thread-id/2652444
> 
> And I agree with @vlsi that it's strange that `pg_stat_activity.query_id` isn't calculated by the server/backend, with `preferQueryMode=extended` 
Well .... we don't control everything :(