From: | Andreas Seltenreich <seltenreich(at)gmx(dot)de> |
---|---|
To: | help-gnu-emacs(at)gnu(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: failure to connect to postgres DB via pg.el |
Date: | 2006-10-07 11:54:41 |
Message-ID: | 874pugqr26.fsf@gate450.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Martin Steffen writes:
> worked fine for some years, only that when I changed recently to a new
> linux distribution (from Suse 10 to the latest Fedora core), things broke.
[...]
> - or postgres applies tougher access restrictions on
> the new linux distribution, and therefore rejects me
>
> What is strange, however, is that I can access the
> running data base as "user-name" using the command-line
> tool psql just fine, without being rejected.
[...]
> signal(error ("Backend error: FATAL: Ident authentication failed for user \"user-name\"\n"))
Since pg.el only supports connections via tcp, a possible explanation
of psql's differing behavior could be that pg_hba.conf specifies
different authentication methods for unix domain and network sockets.
E.g., while SuSE used the "trust" method for local tcp connections,
Fedora might be using the "ident" method.
The pg_hba.conf file is documented here:
<http://www.postgresql.org/docs/current/static/client-authentication.html>
regards,
andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Arunagiri K | 2006-10-07 12:44:33 | EXECUTE command in stored procedure |
Previous Message | Martin Steffen | 2006-10-07 10:14:00 | failure to connect to postgres DB via pg.el |