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.
Thank you very much for the support and accurate solution.
Erik R. Serrano Saavedra
Ingeniero de Sistemas Informáticos
El lun, 2 dic 2024 a las 17:10, Ron Johnson (<ronljohnsonjr@xxxxxxxxx>) escribió:
On Mon, Dec 2, 2024 at 11:34 AM Erik Serrano <eserranos@xxxxxxxxx> 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 databaseAny 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 <Redacted>, and butter sauce.Don't boil me, I'm still alive.<Redacted> lobster!
