pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: davecramer (@davecramer) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3166: query_id in pg_stat_activity is NULL when connecting from JDBC, but not from psql
Date: Thu, 21 Mar 2024 14:45:04 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

> 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 :(

view thread (17+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://pgjdbc/pgjdbc
  Cc: [email protected], [email protected]
  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: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox