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 1ughdh-006UHM-1u for pgpool-general@arkaria.postgresql.org; Tue, 29 Jul 2025 10:32:57 +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 1ughdg-00HVPZ-3h for pgpool-general@arkaria.postgresql.org; Tue, 29 Jul 2025 10:32:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ughdf-00HVPR-TG for pgpool-general@lists.postgresql.org; Tue, 29 Jul 2025 10:32:56 +0000 Received: from mail-oa1-x35.google.com ([2001:4860:4864:20::35]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ughde-001MgV-1P for pgpool-general@lists.postgresql.org; Tue, 29 Jul 2025 10:32:55 +0000 Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-2ebb468cbb4so4139437fac.2 for ; Tue, 29 Jul 2025 03:32:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1753785173; x=1754389973; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=GERrsseF0NbBxo4pIuK/EokeLMqje8WMdNqD9XxcsfE=; b=SQj4y7qNFYm0UIJ7/KOsghxpYbg/ObkfV0Z8Y12istMtnszmQaGLViOzYBLZVCKILH dvabVQAUvivstD8VxoyQySe7amCZZ3AGA4OI/HOHypgrb3KeKznjYVqtlKOt8972JZAu RbTsyC6vyQ58cLyyYVhXNgIM/FPk2HhUC8haP8Ax2UpTtRJZJAw2PAN32CDMPKur6zli Sitj7PtLjLIcy5568ZBJpE79xuX/YrP7BAakP9+qWpYNmYP92PAI6XpGmlFfpTuxgOtM oUbxMIaduuffDYJ1o1L/No98aHzGplII1OGUZAV65Toguwq6c7hwXf4arfFcjRFT2nzE qKPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753785173; x=1754389973; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=GERrsseF0NbBxo4pIuK/EokeLMqje8WMdNqD9XxcsfE=; b=VqW7M1LHTwSUfBlzFvjkTS33ShPZVQNq3ehJfNKWmsnN1PBWK6wzd8a8CkyD3uE8QI 3166Mn0cqyBLGLa+Mop9kFWI48I43oXuVD3ZiKsYHsHDrg5+8vnwczzEC0CCjBji/1Ye jCLCQPJ81Gi6FY6Ye9YLa6J048HDLTjWIf1kESGez/VG/T5bY/RRrjqLDM+sTWLzY5S2 EQjf7/Q0IpYifBTaPmVMUKNTepdebPoXF8TW5R1Uhu7gNg2rEAus9AnZParpparuYtyK 1dX7HdP8fXmj35gDShsXtnf4EusiVeYQ4heEi3AWMZMOPrpqb8mA4RZY9aj7tpwRDKhe MyhQ== X-Gm-Message-State: AOJu0YzPRhSr6w7H4ySzmlh4LO2YYkQ3Q/yYmWq+l5j2jIoaudNj/AKX rRIv4vTvDeQqZD+mL5tqdvBW4p2A2ZAEifFc3H4+o0y7YbXhzSQSZ0pMxHeiAd0R6ld9FNH6jV3 mrHxnLj6ZnapswMgmvpluteBQNT3vTjq5w9bh X-Gm-Gg: ASbGncu7MvIjdJhZ9PM1dYAZLCcLenG4ruIToSoO8s4dQ2AOBHtRavRgfzRJiL9um6k 3LNnzKkJXfV71MXKDszhMIaggGEsKFGolkW4FiluQIjUMkrNSYQspU9MD+lQw9AojFlkuzTX2Xl S6le4oKTc6gexEEfS0Ac3OUuxtVmoImVc3CPxT+Uw3b3uhGBcuz6UVdEHZ2O/aLkCa48i3648IF e+inGuhZ2y+cxE= X-Google-Smtp-Source: AGHT+IF+k4Lzio5HToHvW0AO2Yf61vnsMwJdC4NZeNJAMDOvn66ShZ/vO4+9nJGpdlLeFd5Fa1xg+Y6MR5rYePPGsoQ= X-Received: by 2002:a05:6870:1ecf:b0:2e9:e2e6:4a20 with SMTP id 586e51a60fabf-3070197f83amr9660653fac.16.1753785173196; Tue, 29 Jul 2025 03:32:53 -0700 (PDT) MIME-Version: 1.0 From: Luca Ferrari Date: Tue, 29 Jul 2025 12:32:17 +0200 X-Gm-Features: Ac12FXznLNBR6sSl5CuIMDbfKxQZWnhV-FzZ_sBrBeoqYusaSKsoQilF6gmjgSQ Message-ID: Subject: main vs primary 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, sorry for the trivial question, but I cannot find this in documentation, so please indicate me where I can find (in case I missed). What is the difference between main and primary nodes? For example, in my logs I've: LOG: failover: 2 follow backends have been degenerated LOG: failover: set new primary node: 1 LOG: failover: set new main node: 2 in my scenario, the third host (so number 2) has been promoted. So what is the "primary" node 1 doing? Thanks, Luca