Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Ashis Anand <Ashish(dot)The(dot)Dev(at)Gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate
Date: 2009-12-19 00:27:22
Message-ID: 20091219002722.GX4055@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Ashis Anand escribió:

> Problem Statement: PGUSER has to be set for PSQL to authenticate. If left
> unset the connection to database fails with the error mentioned below.
>
> STEPS:
> 1. Install PostgreSQL.
> 2. Start psql from start menu
> 3. create a role for the user 'foo' through the following statement
> CREATE ROLE foo LOGIN CREATEDB CREATEROLE PASSWORD 'bar'
> 4. Create a database mydb
> CREATE DATABASE mydb WITH OWNER = foo
> 5. Open your normal console where pguser is not set
> 6. Run: "psql mydb"
> 7. Enter the password as 'bar'
>
> Actual output:
> psql: FATAL: password authentication failed for user "foo"

Hmm. Do you have a pgpass.conf file with a conflicting password for
user foo?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ashish Anand 2009-12-19 07:52:59 Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate
Previous Message Nagy Daniel 2009-12-18 11:11:04 Re: BUG #5238: frequent signal 11 segfaults