Re: BUG #15025: PSQL CLI - inconsistency when both -d and -U supplies a username - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15025: PSQL CLI - inconsistency when both -d and -U supplies a username
Date
Msg-id 29202.1517168326@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #15025: PSQL CLI - inconsistency when both -d and -Usupplies a username  (Bruce Momjian <bruce@momjian.us>)
Responses Re: BUG #15025: PSQL CLI - inconsistency when both -d and -Usupplies a username
List pgsql-bugs
Bruce Momjian <bruce@momjian.us> writes:
>     psql -d "postgresql://user2@momjian.us/test" -U user1
> -->    Password for user user1:
> but it wants the user2 password.

> It doesn't matter whether -U is first or last, it always prompts for the
> -U user, but connects as the -d user.

Bleah.

> Because the URI is parsed by libpq, I don't think we can do any better
> than just suppress the user name in the password prompt when a URI is
> used.

That doesn't seem very user-friendly at all.  I think that the most
correct behavior in this case would be to throw an error because of the
conflicting command line parameters.  Now admittedly, psql doesn't throw
an error for

    psql -U alice -U bob

so maybe just silently making a choice is OK, but we need to be clear
as to which choice we made.  Isn't it possible to get the URI parse
results back out of libpq?

            regards, tom lane


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15033: Segmentation fault running a query
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #15025: PSQL CLI - inconsistency when both -d and -Usupplies a username