On Tue, 2004-05-25 at 02:36, Tom Allison wrote:
So the tcpip_socket=yes statement has nothing to do with TCP/IP
connection? While tcpip_sockets=no is the default from postgres, the
configuration file in Debian shows otherwise.
tcpip_socket=yes makes the postmaster listen for TCP/IP
J.H.M. Dassen (Ray) wrote:
On Sun, May 23, 2004 at 14:46:34 -0400, Tom Allison wrote:
J.H.M. Dassen (Ray) wrote:
PostgreSQL doesn't care about /etc/passwd. The default client
authentication settings care about what user is connecting to the
database server through a UNIX socket.
Gee I must have
On Sat, May 22, 2004 at 19:36:38 -0400, Tom Allison wrote:
I created a user in psql but now I can't log in as that user.
I get an error
psql: FATAL: IDENT authentication failed for user dbmail
This implies that I need to have all my users for pgsql listed in both
the /etc/passwd file
J.H.M. Dassen (Ray) wrote:
On Sat, May 22, 2004 at 19:36:38 -0400, Tom Allison wrote:
I created a user in psql but now I can't log in as that user.
I get an error
psql: FATAL: IDENT authentication failed for user dbmail
This implies that I need to have all my users for pgsql listed in both
the
On Sun, May 23, 2004 at 14:46:34 -0400, Tom Allison wrote:
J.H.M. Dassen (Ray) wrote:
PostgreSQL doesn't care about /etc/passwd. The default client
authentication settings care about what user is connecting to the
database server through a UNIX socket.
Gee I must have missed something in the
stuck.
I created a user in psql but now I can't log in as that user.
I get an error
psql: FATAL: IDENT authentication failed for user dbmail
This implies that I need to have all my users for pgsql listed in both
the /etc/passwd file and the postgres database. Or does postgres just
us the
6 matches
Mail list logo
