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 1tVlKw-00BEfK-LO for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 05:44:07 +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 1tVlKv-00CbXK-Ln for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 05:44:05 +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 1tVlKv-00CbXC-AM for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 05:44:04 +0000 Received: from mail-oi1-x235.google.com ([2607:f8b0:4864:20::235]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tVlKs-000eSG-3A for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 05:44:04 +0000 Received: by mail-oi1-x235.google.com with SMTP id 5614622812f47-3eb7edfa42dso263515b6e.2 for ; Wed, 08 Jan 2025 21:44:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1736401443; x=1737006243; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iJ8QvCCNoJy4GIIrUMZJdEL616XlqIapwCIRUys/11Y=; b=dnhiYUrCTLKhihMiglTOCiQV2FbXOXYOu/AO4E+x8GNX9ZMFSORT9stFMwNc8DWlRk X+EJ0HJz0cTwu3+xupf7M+D5W6cYapKAxScHLdBcjsy2Hvhxxkc6oihjtxK8xi4rJAj/ BWWLCkm5rcvrDEu3BUW5rZ7s6IWBbz7eT9sZi/4inbvqFCHXb3kax/75mFLxKIAPjPfT aIEhKr6X5binrB4x4Wydw6TGTjCQCXOfuo3vSskrsZu8I14D+oYNuRAs0bi/2h27sLC1 QmTgNrs47zp/cXpc6/A9wFyJPs/g1ESroClHANXptuKw3Djks+ilWH2tdjTir56bEYw1 DqzA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1736401443; x=1737006243; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iJ8QvCCNoJy4GIIrUMZJdEL616XlqIapwCIRUys/11Y=; b=Ue4j/NWOoFeAZ5mPBOeA/RTndLsGf7F/XjUWbVENDJXXsMR2oJJWNIzt1IzrxrdFsF 82RYkZRAejxf+JfaTs/JLOrJ1TBMrWBwZbTeUCcTSYm9V8LHzonXicT5IUUwDEzCuvGu dI/WRPqjkTV4AOs2sDHyp6aKOx4Wf96lXJhXg80fOWKHSMHpdEePLFxKw07Xas3QWCKP r90zeWIaCdFBc08Y970NuWTJ7ZY1/WUXZcN4432iBhIDJ3GVIm2utm2L6RIQiMsI3YwX fkOAOiyp7IL23DJH9uDhgm2y6162aLvqbaQ1bA4r2D9rmIH7XihNBpbhf4ou+Agmh9mD XH8w== X-Gm-Message-State: AOJu0Yw3NHYcxORZ7iCectnlFjbHgR+mYJgU3/DdIl1t4H3fb7PlMssK 7feMknrHCAHBox6keLQVg6pdAVxM6Mx6PEuchIlFyf/6bqfDgT367ioV+2qV10X3fcd1BMmQAbG e6dDKuOifmCVSxfdi+UYHf9ix+OQ= X-Gm-Gg: ASbGnctD47EBo2lJMMErYI5j4jCX318vGlLT2y7NFHyjf+AcLMeVZtUX1p/RqeF0c1d 4L0J3c8FW4yHTh3tIn7sp5omTFGb/em8PodBHAw== X-Google-Smtp-Source: AGHT+IErRvYNXRhtB6Cy5f2tpQ53vInxrIw7su4my+5jR7pGBn+W8rJ9JqfpIEwlN920I/K/9ygEln14XpPIv7jromI= X-Received: by 2002:a05:6808:309f:b0:3e7:a201:db0f with SMTP id 5614622812f47-3ef2ecb1fadmr2835659b6e.25.1736401442693; Wed, 08 Jan 2025 21:44:02 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6802:1a87:b0:577:9519:f64a with HTTP; Wed, 8 Jan 2025 21:44:02 -0800 (PST) In-Reply-To: References: From: "David G. Johnston" Date: Wed, 8 Jan 2025 22:44:02 -0700 X-Gm-Features: AbW1kvZD_b6GIYk7mJNAQcV-RmFhRI2sssoLubov-ZTRuTJ61NI_HeZM3gnCntE Message-ID: Subject: Re: Issue with Password Authentication for Pgpool To: vijay patil Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000002deaea062b3f7718" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002deaea062b3f7718 Content-Type: text/plain; charset="UTF-8" On Wednesday, January 8, 2025, vijay patil wrote: > This behavior might be related to how Pgpool handles authentication. > Having never used pgpool I very well could be wrong but from what I can gather what you want to do is simply not possible within the current design of pgpool. Namely you have multiple nodes so cannot rely on raw mode but raw mode is required for the kind of pass-through auth you are trying. Instead you require pool_hba.conf which itself requires the password file. David J. --0000000000002deaea062b3f7718 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, January 8, 2025, vijay patil <vijay.postgres@gmail.com> wrote:

This behavior might be = related to how Pgpool handles authentication.

<= div>
Having never used pgpool I very well could be wrong but = from what I can gather what you want to do is simply not possible within th= e current design of pgpool.=C2=A0 Namely you have multiple nodes so cannot = rely on raw mode but raw mode is required for the kind of pass-through auth= you are trying.=C2=A0 Instead you require pool_hba.conf which itself requi= res the password file.

David J.

--0000000000002deaea062b3f7718--