public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Tom Lane <[email protected]>
Cc: Martin Pitt <[email protected]>
Cc: PostgreSQL Bugs <[email protected]>
Subject: Re: Fwd: Bug#308535: postgresql-client: [psql] manual page does
Date: Sat, 14 May 2005 12:40:15 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Tom Lane wrote:
> Martin Pitt <[email protected]> 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
  [email protected]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

view thread (9+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Fwd: Bug#308535: postgresql-client: [psql] manual page does
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox