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 1tVmt9-00BRb3-9S for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 07:23:31 +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 1tVmt8-00E12d-Eu for pgsql-general@arkaria.postgresql.org; Thu, 09 Jan 2025 07:23:30 +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.94.2) (envelope-from ) id 1tVmt8-00E12V-4J for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 07:23:29 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tVmt4-000gvR-1m for pgsql-general@lists.postgresql.org; Thu, 09 Jan 2025 07:23:29 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=ClJ1Li23xmhF6dsjyoUF3+oePYg8bzxeBoNgHyJV39E=; b=FKtfgrD1YIg1TSToOP5NLwgJxN c2TAANO58F4zwJnTRmU5inBY1aJLOs97Sj6nasafyZ02FKRbbF1x1QlzfxGGTACGNPtX99v2blVke wqZSKChJh+ReGdcsQY7imBAUY6/OLfXxIkZdmhENsfmRcJvweasaFhOqqXyvyrrb8yuOvBY9o4oB5 R4UKsdPX/dlUysg9P1SXlGkHK0X8lLGomePO3LNzOtBMxiZat+OMUET9SnOdBkZuFLYa0fRkyhtG8 BuhQKptojAd/TkISJ4waTSXcxuyiSAQ0DGlj47o1vgO/Qlwj0IzZQDq+Wcz1CIE3tUWORy64RIlGc 7uA0t0aQ==; Received: from [2409:11:4120:300:caa4:8496:6c90:c0c7] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (Exim 4.94.2) (envelope-from ) id 1tVmt1-001nbQ-8m; Thu, 09 Jan 2025 07:23:26 +0000 Date: Thu, 09 Jan 2025 16:23:19 +0900 (JST) Message-Id: <20250109.162319.54775553046195699.ishii@postgresql.org> To: vijay.postgres@gmail.com Cc: david.g.johnston@gmail.com, pgsql-general@lists.postgresql.org Subject: Re: Issue with Password Authentication for Pgpool From: Tatsuo Ishii In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:caa4:8496:6c90:c0c7 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > If we plan to use pool_hba.conf, then we must use the pool_passwd file to > maintain passwords for all database users. This approach requires that > every time a new user is created, their password is added to the pool_passwd > file. Not really. You can use pool_hba.conf with the auth method to 'password'. With this setting, if a passowrd is not found in pool_passwd, then pgpool asks the password to PostgreSQL. Best reagards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp