Upgrade Failover Cluster

2025-12-03 Thread BUBACZ Martin
Hi All, I'm fairly new to postgresql and I have a question concerning upgrading a 2 node failover physical replication cluster. I'm automating the cluster installation and maintenance by using Puppet. All runs good so far. When it comes to an upgrade scenario, let's say upgrading from rel. 16.x

Re: Interaction between "client_connection_check_interval" and "log_lock_waits" parameters

2025-12-03 Thread Tom Lane
Alfonso Escribano writes: > When client_connection_check_interval has any value, and > log_lock_waits is enabled, the postgresql log displays a message > about lock waits with the frequency of > client_connection_check_interval. When log_lock_waits is enabled, we'll print that "st

Re: Interaction between "client_connection_check_interval" and "log_lock_waits" parameters

2025-12-03 Thread Alfonso Escribano
Hello, I have test it with postgresql 17.7 I have been searching on postgresql src for commits related with client_connection_check_interval, and I only see initial commits in postgresql 14, I think it happends in all versions from 14 until 18, but I can only confirm

Re: Interaction between "client_connection_check_interval" and "log_lock_waits" parameters

2025-12-03 Thread Adrian Klaver
On 12/3/25 00:24, Alfonso Escribano wrote: Hello, I have seen an interaction between "client_connection_check_interval" and "log_lock_waits" parameters that it isn't documented (or I can't find it anywhere). What version of Postgres? Regards, Alfonso Escribano -- Adrian Klaver adrian.kla.

Interaction between "client_connection_check_interval" and "log_lock_waits" parameters

2025-12-03 Thread Alfonso Escribano
Hello, I have seen an interaction between "client_connection_check_interval" and "log_lock_waits" parameters that it isn't documented (or I can't find it anywhere). I don't know if it is a bug or if it is desired behaviour. When client_connection_check_interval h