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.96) (envelope-from ) id 1vVv7O-009j10-1m for pgpool-general@arkaria.postgresql.org; Wed, 17 Dec 2025 17:15:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vVv7N-00F49O-1o for pgpool-general@arkaria.postgresql.org; Wed, 17 Dec 2025 17:15:18 +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.96) (envelope-from ) id 1vVv7N-00F49G-1E for pgpool-general@lists.postgresql.org; Wed, 17 Dec 2025 17:15:18 +0000 Received: from mail-ot1-x32e.google.com ([2607:f8b0:4864:20::32e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1vVv7L-001Gcl-0u for pgpool-general@lists.postgresql.org; Wed, 17 Dec 2025 17:15:17 +0000 Received: by mail-ot1-x32e.google.com with SMTP id 46e09a7af769-7c6ce4f65f7so5209839a34.0 for ; Wed, 17 Dec 2025 09:15:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1765991713; x=1766596513; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=mSXtqWqaIxNj71u1IAIemczpD6Nn2orTSyrch/KL37w=; b=X/7f3sgaKZvNGr2pktYyWBxECV4mEU9dSUS8dF4/0EgWKrJJo5reiwQKxDvl0E5sts wqIgHKQ+NBJDTFsJkFzabfiCHPl6j2LlX5qOt5WCae1lbKI7XAQiU9GorgzhWMZKYMSE hcVOsl8qMp2wcXbS08UM76PBGGFc6kReARhzem7zYtKB1wXI8bL6k7pyc3ND4CUpFk1G WrM3qUwZFweNTpOHbdIgO4lRk7419PA+w/skhIJTkpVqq6h+mQI+lejLhN5ZsaLgDKRz IH+pEa5412SXMHmjn7bwYjyrICDxOAYzUCIdD30NcVJiQjjqt6WzKMZLqtlyE4rLOkxa vu9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1765991713; x=1766596513; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mSXtqWqaIxNj71u1IAIemczpD6Nn2orTSyrch/KL37w=; b=XwJQayzqavI+XUWaECLgD3BAocAG3YweqAww7hLkxMlM8OSoPuFMSoNDflbM6KnUD2 dolui1q9tXxUEstGcMZE6ixwMvg/IrRrUjzjhWGv7jfWVO8pRfPzMEdEsdytSfBBoK1R nC4kauAXFRYyIDQq/j3RCk3Loiu0HH49V+v1K/B1DTABiwT2pKlXTZhaR8WejMDsT76/ 4ju4KKCwptGWSNHv6c00tW6Sj1CgJlDfioqiNpeBVvlRLWJuq9KrEXiWZxcwhVX7o8cP Hm+OwUfXkXvnVdvCHqFce0frdknoxcPORXcAbLVniqJF02i+K1qM4DoSDllzGY2NSV3j 8ylg== X-Gm-Message-State: AOJu0Yx5zCG4I4xGC4lHk4W5Z+P9T2jK86VB77pBjtY69t6qr9bYcPr0 DStPtHtw+r+9HIRAP3pMCNA9ADj7nXKwbI/yIPJ3i1qIapPGeAozrXi2p9SOG5KSnY+t9w5lonK /XE7f5q7qi/Zy6c4nn4nKcQ6WJ6Hn4MU8FaQz X-Gm-Gg: AY/fxX450TCF/Itw+CM9DzqttDh8FLZdVgPYLX1KCn6bx9yOaiDWkV1UbOsOao+f3Fk HCuLUSjA5ncPB7L9ZCpuGOU0yJtHjvnppBh1sONNqsBOzVRqLe9orj77M3OV5QpLcDYvF7hHH0v XuC0c3EaALGLaGC8r+3yZAmpo2LBm7U34taCEtMYgkjqndtSUhz7f/O5mGRlfXulpBb/cihehEa Wut2sZQ76eP9YzmmvcBRMM79UxkaEcNxmek58OPPkkyLRYQCoLgF/g9YOT5YdzyWcIV X-Google-Smtp-Source: AGHT+IHEa884i+ySo1vqouOC2r5NTK/RXF4mku742vm6/Yp9t5ZbZbdxB4AqpzfWAPyZmseDW2kq8QcNzs4M9+cAOlI= X-Received: by 2002:a05:6830:4491:b0:7c7:6479:38d0 with SMTP id 46e09a7af769-7cae835d88dmr9850777a34.22.1765991713203; Wed, 17 Dec 2025 09:15:13 -0800 (PST) MIME-Version: 1.0 From: Luca Ferrari Date: Wed, 17 Dec 2025 18:14:36 +0100 X-Gm-Features: AQt7F2phTaFK9cb43aKHkcTNP3ikIPoeW8gFPKoXFbprxqdLemgHAULAqIoUK2k Message-ID: Subject: pcp_promote_node and watchdog To: pgpool-general@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi all, I don't understand if using pcp_promote_node --switchover () implies also a watchdog status change, as it seems to me this is not the case. Assuming I have a current pimrary and main node, and I want to promote another node in the cluster, what is the correct way to make the watchdog ip to migrate to the promoted primary? Thanks, Luca