Cc: Thomas Kellerer ; pgsql-general@lists.postgresql.org
> Subject: Re: [EXT] DBeaver session populating pg_stat_activity.backend_xmin
> > On Jan 25, 2023, at 14:21, Dirschel, Steve
> > wrote:
> > From my perspective "idle in transaction" isn't necessarily a pr
> On Jan 25, 2023, at 14:21, Dirschel, Steve
> wrote:
> From my perspective "idle in transaction" isn't necessarily a problem
> (although I don't like seeing sessions sitting like that for a long time).
> The problem is when pg_stat_activity.backend_xmin is populated- that can
> prevent a
On 1/25/23 16:21, Dirschel, Steve wrote:
[snip]
The problem is users will connect using DBeaver and their sessions
will sit idle.
Idle is not a problem, "idle in transaction" is.
From my perspective "idle in transaction" isn't necessarily a problem
(although I don't like seeing sessions sitti
>> When I connect to the database through DBeaver with those 2 default
>> settings changed and find that session in pg_stat_activity column
>> xact_start is populated along with backend_xmin. Those get populated
>> just by logging in.
>As you found out in the log, the driver runs DbEaver run m
Dirschel, Steve schrieb am 25.01.2023 um 20:36:
When I connect to the database through DBeaver with those 2 default
settings changed and find that session in pg_stat_activity column
xact_start is populated along with backend_xmin. Those get
populated just by logging in.
As you found out in the
Not sure if anyone on this list may have ideas on this or not. I will also try
and find a DBeaver e-mail list and send to that also.
We are running into a problem where users will connect to a database through
DBeaver. I have found if I leave all DBeaver options as default this issue
does not
