--ZwgA9U+XZDXt4+m+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi PostgreSQL developers!

We recently got the bug report below. Do you agree that documenting
~/.pgpass in psql(1) is a good idea?

Thanks for considering and have a nice day!

Martin

----- Forwarded message from Jari Aalto <jari.aalto (AT) cante (DOT) net> -----

Subject: Bug#308535: postgresql-client: [psql] manual page does not documen=
t ~/.pgpass file
Reply-To: Jari Aalto <jari.aalto (AT) cante (DOT) net>, 308535 (AT) bugs (DOT) debian.org
=46rom: Jari Aalto <jari.aalto (AT) cante (DOT) net>
To: Debian Bug Tracking System <submit (AT) bugs (DOT) debian.org>
Date: Tue, 10 May 2005 23:26:00 +0300
X-Spam-Status: No, score=3D0.0 required=3D4.0 tests=3DAWL,BAYES_50 autolear=
n=3Dno=20
version=3D3.0.2

Package: postgresql-client
Version: 7.4.7-6
Severity: minor

psql(1) manual page does not mention in the FILES section ~/.pgpass file
and how it is used. It should include:=20

FILES

...

o The file ~/.pgpass in is a file that can contain passwords to be
used if the connection requires a password (and no password has
been specified otherwise). This file should have lines of the
following format:

hostnameort:database:usernameassword

Each of the first four fields may be a literal value, or *, which
matches anything. The password field from the first line that matches
the current connection parameters will be used. (Therefore, put
more-specific entries first when you are using wildcards.) If an entry
needs to contain : or \, escape this character with \.

The permissions on .pgpass must disallow any access to world or group;
achieve this by the command chmod 0600 ~/.pgpass. If the permissions
are less strict than this, the file will be ignored.

This explanation was exerpted from=20
http://www.postgresql.org/docs/7.4/s...pq-pgpass.html
I have no idea why it is there, where nobidy is looking

----- End forwarded message -----

--=20
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntulinux.org
Debian Developer http://www.debian.org

--ZwgA9U+XZDXt4+m+
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCg7/uDecnbV4Fd/IRAq4HAKDrqLCbN6Eph32voWvb4wmO+UK3DwCgypVF
TOgxng5Su9Je8oQ1RKL1aZw=
=PjWr
-----END PGP SIGNATURE-----

--ZwgA9U+XZDXt4+m+--

Martin Pitt <mpitt (AT) debian (DOT) org> writes:
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?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

--9jxsPFA5p3P2qPhR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi!

Tom Lane [2005-05-13 9:49 -0400]:
A prominent pointer (URL and hint to local documentation) would
certainly be adequate then.

Thanks and have a nice weekend!

Martin

--=20
Martin Pitt http://www.piware.de
Ubuntu Developer http://www.ubuntulinux.org
Debian Developer http://www.debian.org

--9jxsPFA5p3P2qPhR
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFChNCsDecnbV4Fd/IRAvKNAJ46wqxH6Mhu9CR1eyCQ45o3LO1tzwCfWMs2
HduBD/3OvhDMX7+v2cf31Qg=
=J/Vq
-----END PGP SIGNATURE-----

--9jxsPFA5p3P2qPhR--