Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate - Mailing list pgsql-bugs

From Ashish Anand
Subject Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate
Date
Msg-id c92445880912182352i7859e69ekf30d71768cd4e3b2@mail.gmail.com
Whole thread Raw
In response to Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-bugs
Yes, the file is there as of now and its contents are:
localhost:5432:*:postgres:bar


I am not sure if the file was there when it actually happened. But the repro
steps are complete in themselves and can be reproed on any fresh install of
ver 8.4.1.

Thanks,
Ashish.

On Sat, Dec 19, 2009 at 5:57 AM, Alvaro Herrera
<alvherre@commandprompt.com>wrote:

> Ashis Anand escribi=F3:
>
> > Problem Statement: PGUSER has to be set for PSQL to authenticate. If le=
ft
> > 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 =3D 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.
>

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #5249: PGUSER has to be set in the console for PSQL to authenticate
Next
From: Nagy Daniel
Date:
Subject: Re: BUG #5238: frequent signal 11 segfaults