Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pKoLQ-0002qW-SX for pgsql-general@arkaria.postgresql.org; Wed, 25 Jan 2023 22:34:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pKoLP-00023o-PZ for pgsql-general@arkaria.postgresql.org; Wed, 25 Jan 2023 22:34:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pKoLP-00023c-Dw for pgsql-general@lists.postgresql.org; Wed, 25 Jan 2023 22:34:15 +0000 Received: from mail-qt1-x82a.google.com ([2607:f8b0:4864:20::82a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pKoLL-0000WR-5j for pgsql-general@lists.postgresql.org; Wed, 25 Jan 2023 22:34:15 +0000 Received: by mail-qt1-x82a.google.com with SMTP id x5so17581811qti.3 for ; Wed, 25 Jan 2023 14:34:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=YpAY8wqv2WzlaoGCG+av7sYOOoYHrvZJh/kRZDtMz90=; b=nBJWAFK17GCfy8YPkZFPgeRVep6ZuKgavabi9Shv84OZKfMIRGaDBrq1u8NFrMKZ4Z zF26ilhFJkrGcIrTBEGojNDLqtjNLY5JuAwyGcC8eAqYudbxpfsAoAT7y4bNyTum738+ eWYTsTCigY33Zj0LXd6Kj7BFPYYoQrqG9d0ninYCh8ibj4LyYdHvEQDwEW/N1GXVEmzB qFs8dOjiSmczpAk6lRxJdIqj5WQRkFd2lvyjnNuoHgCcI3WQVxW1zFpwrdlPnJAHFcHK vvaqDWu9s7hyMXlpdM1+vTFASV5KOhJurjiA/5WGXG/rI7dsnQ4Z/ptZJ4wQiEOqghU4 oATQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=YpAY8wqv2WzlaoGCG+av7sYOOoYHrvZJh/kRZDtMz90=; b=Czam79/9XbiH0Qltrl5T0QAbiIyi6r0axfpXnpxazwbXQIgq4bHEb6LZcaBYLM6Rui EmyI8n3Jln1aQsYYRfp3Jvo1gEoCba63fktOOfE4rKsv3utVqEwDxR/+gDrShlf20gS1 KFC6nt/yCMadeyYUkMS1UxhgCs7oJFcXHsR0HTCSjFKs62Aeg9jqVmhUsSyRiw8no0TO SqMC6Db2e91Kk0hol+C5dXwmbOBiALidwLfi2Z8Is9h6FO5kJAUkAR1508k/hmdGopny 12nnkewoNs7AcUDwA7QbD4JjuwVJNbX4M1Oxv9AwSrtO5ydw2J6g0jO5Esg/JFLpKaqA N6eQ== X-Gm-Message-State: AO0yUKUqO1bbXLniCdtVthQv8asgLfaV28h82uS8mptMlFJD8SYsH3JE cT3tv00KjlHSj4YuuUIh/80NK8t0FVI= X-Google-Smtp-Source: AK7set9gyvEG+VepBWU7vFwq+Wl5GVehqSao5vZ2wCFVVPitUxina1nrWAClTDcYazdqFmcPyjTcwg== X-Received: by 2002:a05:622a:178e:b0:3b6:31e3:1a59 with SMTP id s14-20020a05622a178e00b003b631e31a59mr7806358qtk.40.1674686049317; Wed, 25 Jan 2023 14:34:09 -0800 (PST) Received: from [192.168.1.66] (108-250-206-84.lightspeed.nworla.sbcglobal.net. [108.250.206.84]) by smtp.googlemail.com with ESMTPSA id q16-20020ae9e410000000b006ec62032d3dsm4391317qkc.30.2023.01.25.14.34.08 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 25 Jan 2023 14:34:08 -0800 (PST) Content-Type: multipart/alternative; boundary="------------uSrHK7MUASvaysjoQyykgVT9" Message-ID: <9ff830d1-1432-bd07-46f0-5975ef88271c@gmail.com> Date: Wed, 25 Jan 2023 16:34:08 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [EXT] Re: DBeaver session populating pg_stat_activity.backend_xmin Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------uSrHK7MUASvaysjoQyykgVT9 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 sitting like that for a long time). Well, it is, since you /are/ sitting in an open transaction. This fixes it: idle_in_transaction_session_timeout https://www.postgresql.org/docs/9.6/runtime-config-client.html -- Born in Arizona, moved to Babylonia. --------------uSrHK7MUASvaysjoQyykgVT9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit 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.