From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Mika Fischer <mf+ubuntu(at)zoopnet(dot)de> |
Subject: | Re: BUG #4040: psql should provide option to not prompt for password |
Date: | 2008-03-17 17:52:18 |
Message-ID: | 20080317175218.GG4317@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Peter Eisentraut wrote:
> Am Montag, 17. März 2008 schrieb Tom Lane:
> > It's not, IMHO. You don't even know if the local database is where the
> > user is intending to connect to. Moreover this presupposes some rather
> > obsolete ideas about what connection parameters might need to be given
> > on the command line.
>
> "psql <TAB>" to complete the local database names is a very useful feature
> that has existed and been in use for a long time.
Agreed. If it can be made to work with remote database when the user
already provided the -h option, even better. (And while at it,
providing options for -h completion from .pgpass would be neat too.)
BTW while reading the psql manpage I noticed this statement:
A popular application of this facility is to refer to the last
inserted OID in subsequent statements to build a foreign key
scenario.
(This refers to :foo interpolation.) Talking about popular application
of OIDs in FKs seems so 90's. Should we remove that phrase?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-03-17 19:41:29 | Re: BUG #4040: psql should provide option to not prompt for password |
Previous Message | Peter Eisentraut | 2008-03-17 17:13:08 | Re: BUG #4040: psql should provide option to not prompt for password |