X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id CB97253CC5 for ; Fri, 6 May 2005 00:03:49 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23355-05 for ; Fri, 6 May 2005 03:03:38 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 2BAA753C5E for ; Fri, 6 May 2005 00:03:36 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j4633VCJ009356; Thu, 5 May 2005 23:03:31 -0400 (EDT) To: "Michael J. Robinson" Cc: pgsql-admin@postgresql.org Subject: Re: Problem setting up new users In-reply-to: References: Comments: In-reply-to "Michael J. Robinson" message dated "Thu, 05 May 2005 16:17:55 -0400" Date: Thu, 05 May 2005 23:03:31 -0400 Message-ID: <9355.1115348611@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/62 X-Sequence-Number: 17491 "Michael J. Robinson" writes: > When I try to login I get the following error: > [root@host postgressql]# psql template1 -U foo --password > Password: > psql: FATAL: IDENT authentication failed for user "foo" The prompt tells the tale: you aren't "foo", you are "root". IDENT wants those things to be the same. The password you forced psql to ask you for is totally irrelevant. Probably your best bet is to "su" from root to postgres and then create your initial users as postgres. You can create root as a postgres superuser if you would prefer to do this sort of maintenance from the root account in future. (Whether that's a good idea is another question --- in general, using root for more than you absolutely must isn't good practice IMHO.) You could also think about changing to some other auth method besides IDENT, if you would prefer to operate with Postgres passwords instead of who-are-you-to-the-kernel. regards, tom lane