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 1tIAxO-00CgNS-UR for pgsql-admin@arkaria.postgresql.org; Mon, 02 Dec 2024 18:15:39 +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 1tIAxL-002IKm-WE for pgsql-admin@arkaria.postgresql.org; Mon, 02 Dec 2024 18:15:37 +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 1tIAxL-002IKN-Ic for pgsql-admin@lists.postgresql.org; Mon, 02 Dec 2024 18:15:36 +0000 Received: from mail-lf1-x129.google.com ([2a00:1450:4864:20::129]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIAxF-000h4h-MY for pgsql-admin@lists.postgresql.org; Mon, 02 Dec 2024 18:15:36 +0000 Received: by mail-lf1-x129.google.com with SMTP id 2adb3069b0e04-53df67d6659so6973599e87.3 for ; Mon, 02 Dec 2024 10:15:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1733163329; x=1733768129; 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=gpNFzlV6fnepDAQavs6NsQoFGs2JKAI7tSToxvOvHEA=; b=L+25idC3d/2ypjogdidBDpIVNNpyMwHsyTZpr5+ityj+19HN3QHbeCjQQ/cMLS9gml d3icBMbNwffouXCFF1YkzVd+WYTlU1ziKE/krFwPzhXCYZrVqqa/q78FtoNLWU8K3fp8 ytD3xMU708U1tx/CIbEdImijI/wa59QMQW0reYwu01mJuC1rcVqmacJfOChw4IlEKi4c 0ksg9VTmZC2GGuXnaYgBkFrUmTP8dkatcsZodeXT77aE2nAUitu+o3DV5K2563FVggGM /+0pT1I0AsvnieGupSkH38AHtao2GXGUoZPdi/nGtoKYmFSZjppA9f7ahII7sLy725oK 4aMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733163329; x=1733768129; 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=gpNFzlV6fnepDAQavs6NsQoFGs2JKAI7tSToxvOvHEA=; b=FVP4vUde6QobJJRrDZFw/FCvenrQzn+2hFURqsLdXy1A83SR1fTxeYAZaKTWwsc59q TEDTHhRYF46/vS/+MYuvBO6rFUa3DhdlZ2k8QXrcQKzKgDmSWAXiLXQQ5KGaMH+88d7B ywR0v2rhBBmmBPiRm14WQ/pmn8y8flL4UhS6V8b+hNZQFRpN8gNDRjDKaCGpa7qGyPHJ 0IsyLFYRHG13uhLd8eaOWOy1AU+XUW6V4GNZfxiuBV9gHDNiqSAVmkAZ3WL4S3IRCJXg Uba7SZ3KS4ktHtSlss/G/p6F7SSqL0LsdbwcFG4LH8n2imw9ZcMOmFb0YyqfaHVAYwGE RTRA== X-Gm-Message-State: AOJu0Yw3GjIoi/GzrPrWNW27c319WEIN5cPMMfZf5C8/QMesDDUMU6j2 VjVFOM6G9woo12xhRibxefKNedNS1e+jpgWWj9WNhUhs9j8OJ2oOsbGst6W11JYauMJLPFBzhVe QMwyeRhItAk/R2AuI4LbdfafAKmCVPg== X-Gm-Gg: ASbGnctaLwxOCRlSG49lkh3r4/m60DOvlcGNcNc62eRyTox7rXgH70eQ1XUpXAtye2b 2VxlrJpIU5KPwoBJn4t/4/t2lYhoAqEq8 X-Google-Smtp-Source: AGHT+IE2CfXXaocyHZQG1mCgJQq7teax62XxllRu7/4e5mejDA9xV2PsXpw6mPuj7Lqy2nsubJunddqWwQ7m5mdvHcE= X-Received: by 2002:a05:6512:3b06:b0:53d:ec46:342e with SMTP id 2adb3069b0e04-53df00a9738mr16673083e87.1.1733163327308; Mon, 02 Dec 2024 10:15:27 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Erik Serrano Date: Mon, 2 Dec 2024 15:15:17 -0300 Message-ID: Subject: Re: Database disconnection due to timeout To: Ozgur Kulu Cc: Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000764c2006284d88ce" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000764c2006284d88ce Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you for your help! *Erik R. Serrano Saavedra* El lun, 2 dic 2024 a las 14:48, Ozgur Kulu () escribi= =C3=B3: > Hi Erik, > > First of all, check statement_timeout parameter on db side. > secondly, ask the developmet team or middleware team timeout settings. > > Regards, > > Erik Serrano , 2 Ara 2024 Pzt, 19:34 tarihinde =C5= =9Funu > yazd=C4=B1: > >> 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. >> >> Thank you very much for your contributions and help. >> Greetings >> >> >> *Erik R. Serrano Saavedra* >> *Ingeniero de Sistemas Inform=C3=A1ticos* >> >> --000000000000764c2006284d88ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thank you for your help!=C2=A0


Erik R. Serrano Saavedra<= /i>



El lun, 2 dic 2024 a las 14:48, Ozgur Kulu (<kuluozgur@gmail.com>) escribi=C3=B3:
Hi Erik,

First of all, check=C2=A0statement_timeout parameter on db= side.
secondly, ask the developmet team or middleware team timeout settings= .

Regards,

Erik Serrano <eserranos@gmail.com>, 2 Ara 2024 Pzt, 19:34 tarihinde =C5=9Funu yazd=C4=B1:
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 p= arameter within the configuration file (postgresql.conf) connection (pg_hba= .conf) or replica manager (repmgr.conf) that allows me to solve this proble= m.


Background:
- The database is in an Azure IaaS.
- The d= atabase allows the connection, but the user drops due to timeout
- I can= connect to the same server and database with their credentials
- Firewa= ll allows the connection.
- the configuration in pg_hba.conf owns the us= er
- user connects through DBeaver
- The database postgreSQL is versi= on 15
- user is the owner of the database

Any c= ontribution is appreciated.

Thank you very much fo= r your contributions and help.
Greetings


Erik R. Serrano Saavedra
Ingeniero de Sistemas Inform=C3=A1ticos
--000000000000764c2006284d88ce--