Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tICks-00Csnt-Ut for pgsql-admin@arkaria.postgresql.org; Mon, 02 Dec 2024 20:10:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tICkq-002wt7-2A for pgsql-admin@arkaria.postgresql.org; Mon, 02 Dec 2024 20:10:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tICkp-002wsy-MM for pgsql-admin@lists.postgresql.org; Mon, 02 Dec 2024 20:10:48 +0000 Received: from mail-ot1-x332.google.com ([2607:f8b0:4864:20::332]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tICkn-000hwG-K0 for pgsql-admin@lists.postgresql.org; Mon, 02 Dec 2024 20:10:48 +0000 Received: by mail-ot1-x332.google.com with SMTP id 46e09a7af769-71d5476ebb1so2059266a34.2 for ; Mon, 02 Dec 2024 12:10:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733170244; x=1733775044; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=6vEpAFNN4sWfifnxXPvktCilwuDy+n+MQkDGdSDUuYU=; b=Q8ZANH1q3wImN6OjbkJh0Vy52AYLO4bmpgcqWI/5VZH1Yr31QQiQm+wqH6AfTvZyoG MoopO+GQ6m0cf6Y11fCeVdsDcEPExYGE889xWTANoovA2p/F/5ZDk47O2LLXFL7qapP3 TADi9b5Te3Idwh1ng2++Sa95GN2UGUFTkIBOUoToLgVj73vRY1VayLQtfAWzFHbSbTwu 0LzFp19RLlcb9zeqYh1s861WOCClwvGpncltEabOdFlU568E+nBCAhX6bSGApmjNuuNa bwJ65p9JsDYdj2YIqMmSEdFMJZgr3x0LnQPtQ/iZ8MCqaCRBEvPr/CpyW10a0kN9yCFA XOPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733170244; x=1733775044; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6vEpAFNN4sWfifnxXPvktCilwuDy+n+MQkDGdSDUuYU=; b=O94iXTFFDorw5mjmmZBOmyt+gx5OhDwnOe5UZ0DQn4HQX/MbwwTmhozs0HeoF9XY9m RdQAborMnAT2myTbjCP/h3mLiABqHJ5bxVoKrpyD6pOjz9ZsnuSWelBrFSxTJfpH+e+6 eGsqK2yAHIOL/Xi/3Ooiq2pyz4vUQRjM5HONtEUASRVvoW+dXEb4ijAux3ix1464Ux6+ t/8/qGpktQNS6dn/KHWjpRPDdi/MWnE74XpwcAFaxyJbowaSEoMDcZHIFH+YZfALMgY2 gSZxEQlImf/YQrugnRJ7N6llErAjIChSbv9YI06gzq58gLyvI5URqkAlmgip8evdBsnB WcuQ== X-Gm-Message-State: AOJu0Yz0t8drI4fduHxBJnNxm29aLxxXjdtiB0voWszxkamTMtXQukjv PrDmYVsq6yqEx2JCqSO/o70e5ZROfp2pIr9Jr825/Um4gQ1FplkVHhcAv17MYL4+QRBmHg5NuAE 23jV7Ws4wgthayIE6qRWfpVcBerup0Q== X-Gm-Gg: ASbGncsvgD38xKPkFibMqW3710peQXkE9O+EL62dtl6dvUKrxEndfVP142xl+tIddR6 DD1JjsG9s3p1j2+KWq7rgTNe2wZa1E6aO42HNR1MoK28XkC1GHxsd2hUbm1dBaEhHxg== X-Google-Smtp-Source: AGHT+IG4aNEh/62FFZC0STABXqy6NlIIOwSQGS8FVq8GQuvXi8l7seUrgL0FeAFN8wADwf+aShO++NjutcVw4bReG8I= X-Received: by 2002:a05:6830:6f0e:b0:71d:54fb:da56 with SMTP id 46e09a7af769-71d65c7aeafmr22939581a34.2.1733170243911; Mon, 02 Dec 2024 12:10:43 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Mon, 2 Dec 2024 15:10:33 -0500 Message-ID: Subject: Re: Database disconnection due to timeout To: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000b945d506284f2413" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b945d506284f2413 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Dec 2, 2024 at 11:34=E2=80=AFAM Erik Serrano = wrote: > Hi guys, nice to meet you .. I have to solve a user problem against the > postgresql database that is located in the Azure cloud as (IaaS) that is > happening to you the following: > > A user drops the connection from his console to the replica slave databas= e > due to timeout, it is possible that there is a parameter within the > configuration file (postgresql.conf) connection (pg_hba.conf) or replica > manager (repmgr.conf) that allows me to solve this problem. > > > Background: > - The database is in an Azure IaaS. > - The database allows the connection, but the user drops due to timeout > - I can connect to the same server and database with their credentials > - Firewall allows the connection. > - the configuration in pg_hba.conf owns the user > - user connects through DBeaver > - The database postgreSQL is version 15 > - user is the owner of the database > > Any contribution is appreciated. > Disconnect during any random query? Disconnect only during a very long-running query? Disconnect when DBeaver is "just sitting there", while the user is doing something else? --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --000000000000b945d506284f2413 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Dec 2, 2024 at 11:34=E2=80=AFAM E= rik Serrano <eserranos@gmail.com<= /a>> wrote:

--
=
Death to <Redacted>, and butter sauce.
Don't= boil me, I'm still alive.
<Redacted> lobster!
=
--000000000000b945d506284f2413--