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 1tIDGc-00Cwh1-Kw for pgsql-admin@arkaria.postgresql.org; Mon, 02 Dec 2024 20:43:38 +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 1tIDGY-003G7Y-Ri for pgsql-admin@arkaria.postgresql.org; Mon, 02 Dec 2024 20:43:36 +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 1tIDGY-003G4W-Ef for pgsql-admin@lists.postgresql.org; Mon, 02 Dec 2024 20:43:35 +0000 Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIDGW-000i9f-MG for pgsql-admin@lists.postgresql.org; Mon, 02 Dec 2024 20:43:35 +0000 Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-53e0844ee50so1996434e87.0 for ; Mon, 02 Dec 2024 12:43:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733172212; x=1733777012; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XxXdWQS5Dlg2pkbNOelbHhZsxc7NI7rbbAO8uUiQL20=; b=GSAfw+6Myv79Nyur5aLJeJM2heD8lZSbl1uVKg9oPobN6YJj1lRn9RVtSPMpEj1beN P/7XA8n3eO9lA+Eh/2SSjqSyY9rULPLhasrnhu7Lk95yuvexLG5zZWdqTzIsSmutEcyv A5e6MUqUN0QsCLz2UMuu4rZxKhU+o9Vb0PEQdOLf75FeFvpRYSycnRCxO8Lz+ZFloEDS 0X+xYWd3SVlaRIliR/N+wo3C/pAV+/rZC0Vndmlp9+CN8mveP5I+2vRjVfFn2IzsibML KqqtlZDSuLau/TjKuUncbGt+L3As2Fj2MhATbh0nRg1Nra2H/slf3lp8hh9vIz+4ZhwQ uPTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733172212; x=1733777012; h=cc: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=XxXdWQS5Dlg2pkbNOelbHhZsxc7NI7rbbAO8uUiQL20=; b=fJPRlnM4QWV3Z0onj5YSFtX2mcwWy5nUg3VtuC366FOY4JXP7FSVVVUlPJMtfI6y3c jUWdJp71g09zuNHeSbdWs1KimZEXDUqiPvOJYZIg8a+i3djXGBzNhqcFcsk8WJfHrAui 56UV8D8++p5ArUarXMn/bi067sVHG6PJk7T9bnt5aKDdAXFNQZPdXi12HBCQBY0nzFmz H7YJKpk45aX+YUU/HquOUvTIsQu1cNaoRnWS8lofS5Vqh881vNUo9bjbH/Woiu7sX89P Hi+4UMJPAnfE2B7eHy6KmHUz4qzFWxptBCkv/SUrB6VUeSNWQJKbKAE+4YspFXCmbDKn 2SPw== X-Gm-Message-State: AOJu0Yz8P5Ijc3ybcrP40Oz8zeaWpooTHNyfQagbTkgx6UXSboUkGN5+ aFKCVRtc7XkF8UIZX+7OwHjoX+UvgJwDrfg7Vd4ZC243MHImLBRDdJMLSQvdjz1mUtGjvy/9X8u fgcQsGCyKldxPHYIS9iZOIj/QmXevkfUy X-Gm-Gg: ASbGncsk10MQij7M+byJDz/RY0HYGDgUUql3yRelsznDyuVwwUuYWGq3VcvTs1CKJDA c7BjSuMdOLbQtpLAu1jo+5Gy/MM/MyPRT X-Google-Smtp-Source: AGHT+IHjcaiuanxar4HffqoZzCBS2xt9o45yaRsOd1omDexKeSdNUXs9HHOIQC9u0yYt/RBeqJcPL5OD6SVv8ON1eFM= X-Received: by 2002:a05:6512:3181:b0:53d:d5be:4bd9 with SMTP id 2adb3069b0e04-53df00cf711mr13569534e87.22.1733172211581; Mon, 02 Dec 2024 12:43:31 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Erik Serrano Date: Mon, 2 Dec 2024 17:43:20 -0300 Message-ID: Subject: Re: Database disconnection due to timeout To: Ron Johnson Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="00000000000001909906284f9a91" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000001909906284f9a91 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Friends, In the end I managed to detect that the failure was caused by a delay in the connection that was established with respect to the timeout parameter that was defined in postgresql.conf. It is adjusted and the user can establish the connection. Additionally, the DBeaver that the user owns presents problems in its JDBC with respect to version PG 15. Thank you very much for the support and accurate solution. *Erik R. Serrano Saavedra* *Ingeniero de Sistemas Inform=C3=A1ticos* El lun, 2 dic 2024 a las 17:10, Ron Johnson () escribi=C3=B3: > 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 >> database 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? > > -- > Death to , and butter sauce. > Don't boil me, I'm still alive. > lobster! > --00000000000001909906284f9a91 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Friends,=C2=A0

In the end I managed to detect that the failure was caused = by a delay in the connection that was established with respect to the timeo= ut parameter that was defined in postgresql.conf. It is adjusted and the us= er can establish the connection. Additionally, the DBeaver that the user ow= ns presents problems in its JDBC with respect to version PG 15.

Than= k you very much for the support and accurate solution.


=
Erik R. Serrano Saavedra
Ingeniero de Sistemas Inf= orm=C3=A1ticos


El lun, 2 dic 2024 a las 17:10, Ron Johnson= (<ronljohnsonjr@gmail.com>) escribi=C3=B3:
Hi guy= s, nice to meet you .. I have to solve a user problem against the postgresq= l database that is located in the Azure cloud as (IaaS) that is happening t= o you the following:

A user drops the connection from his console to= the replica slave database due to timeout, it is possible that there is a = parameter within the configuration file (postgresql.conf) connection (pg_hb= a.conf) or replica manager (repmgr.conf) that allows me to solve this probl= em.


Background:
- The database is in an Azure IaaS.
- The = database allows the connection, but the user drops due to timeout
- I ca= n connect to the same server and database with their credentials
- Firew= all allows the connection.
- the configuration in pg_hba.conf owns the u= ser
- user connects through DBeaver
- The database postgreSQL is vers= ion 15
- user is the owner of the database

Any = contribution is appreciated.

Di= sconnect during any random query?
Disconnect only during a very l= ong-running query?
Disconnect when DBeaver is "just sitting = there", while the user is doing something else?

--
Death to <Redacted>, and bu= tter sauce.
Don't boil me, I'm still alive.
<Re= dacted> lobster!
--00000000000001909906284f9a91--