Tom Lane wrote:
> Martin Pitt <mpitt@debian.org> writes:
> > We recently got the bug report below. Do you agree that documenting
> > ~/.pgpass in psql(1) is a good idea?
>
> On that theory we'd have to replicate large parts of the libpq
> documentation on every one of the "client application" pages,
> which doesn't seem very maintainable. (.pgpass is just the tip
> of the iceberg; the "environment variables" and "SSL support"
> pages are also pretty critical for users to know about.)
>
> I agree that there needs to be some more prominent mention,
> but this doesn't look like the way to do it. Maybe some
> "see also" links?
Have you looked at the current docs? 8.0.3 has this in the second
paragraph of the psql Usage section:
http://www.postgresql.org/docs/8.0/static/app-psql.html
It is also convenient to have a ~/.pgpass file to avoid regularly having
to type in passwords. See Section 27.12 for more information.
This was added in February:
revision 1.133
date: 2005/02/11 04:19:05; author: momjian; state: Exp; lines: +22 -15
Mention that some psql environment variables come from libpq and note
more variables can be found in the libpq manual section.
Mention .pgpass in the psql manual page section dealing with connection
parameters and point to the libpq section for more details.
Is that sufficient?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
