Thread: Fwd: Bug#425125: postgresql-8.1: localhost does not work for unix sockets in ~/.pgpass
Fwd: Bug#425125: postgresql-8.1: localhost does not work for unix sockets in ~/.pgpass
From
Martin Pitt
Date:
Hello PostgreSQL developers, I just got the bug report below from a Debian user. The comment on http://www.postgresql.org/docs/8.1/interactive/libpq-pgpass.html confirms this, it describes the exact same problem. Thank you, Martin ----- Forwarded message from David <wizzardx@gmail.com> ----- X-Spam-Status: No, score=0.0 required=4.0 tests=BAYES_50,UNPARSEABLE_RELAY autolearn=no version=3.1.7-deb Subject: Bug#425125: postgresql-8.1: localhost does not work for unix sockets in ~/.pgpass Reply-To: David <wizzardx@gmail.com>, 425125@bugs.debian.org Date: Sat, 19 May 2007 12:10:18 +0200 From: David <wizzardx@gmail.com> To: Debian Bug Tracking System <submit@bugs.debian.org> Package: postgresql-8.1 Version: 8.1.8-1 Severity: normal According to this page: http://www.postgresql.org/docs/8.1/interactive/libpq-pgpass.html "A hostname of localhost matches both host (TCP) and local (Unix domain socket) connections coming from the local machine." However that does not work for me. I get prompted for a password. I have to put '*' in the hostname section to allow passwordless local unix socket connections. eg: Works: *:*:david:david:moo Does not work: localhost:*:david:david:moo -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=en_ZA, LC_CTYPE=en_ZA (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash -- no debconf information ----- End forwarded message ----- -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org
Re: Fwd: Bug#425125: postgresql-8.1: localhost does not work for unix sockets in ~/.pgpass
From
Tom Lane
Date:
Martin Pitt <martin@piware.de> writes: > I just got the bug report below from a Debian user. The comment on > http://www.postgresql.org/docs/8.1/interactive/libpq-pgpass.html > confirms this, it describes the exact same problem. This seems to be a repeat of http://archives.postgresql.org/pgsql-hackers/2006-05/msg00295.php which was fixed a year ago but only for 8.2 and later, since there was some concern about the change being not backwards compatible. http://archives.postgresql.org/pgsql-committers/2006-05/msg00123.php regards, tom lane