Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 5F6D12E2D94 for ; Mon, 11 Feb 2008 13:15:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 68837-08 for ; Mon, 11 Feb 2008 13:15:02 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 181992E0329 for ; Mon, 11 Feb 2008 13:15:01 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id m1BHExVS003306; Mon, 11 Feb 2008 12:14:59 -0500 (EST) To: Thomas Schuster cc: pgsql-admin@postgresql.org Subject: Re: can't connect with md5 encrypted pw In-reply-to: <1202683846.15629.19.camel@boa> References: <1202683846.15629.19.camel@boa> Comments: In-reply-to Thomas Schuster message dated "Sun, 10 Feb 2008 17:50:46 -0500" Date: Mon, 11 Feb 2008 12:14:59 -0500 Message-ID: <3305.1202750099@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/136 X-Sequence-Number: 28210 Thomas Schuster writes: > my problem: > createdb test > psql -U john -d test -W > password:****** > psql: FATAL: password authentication failed for user "john" Given the facts you show, the most obvious explanation is that you entered the wrong password. You might want to do an ALTER USER PASSWORD command (as the superuser) just to make sure you didn't fat-finger the password setting initially. If that isn't it, try looking into the postmaster log to see if it logs any additional details about the failure. regards, tom lane