Message-ID: <gh-pgjdbc-pgjdbc-3166-c2010034546@github.com>
From: "goranschwarz (@goranschwarz)" <noreply+goranschwarz@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 20 Mar 2024 16:46:16 +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: goranschwarz
X-GitHub-Comment-Id: 2010034546
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-2010034546
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*)

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?   

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`)    

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`