unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Martin Steffen <msteffen@ifi.uio.no>
Cc: pgsql-general@postgresql.org
Subject: failure to connect to postgres DB via pg.el
Date: 07 Oct 2006 12:14:00 +0200	[thread overview]
Message-ID: <m364ewtouv.fsf@cm-84.209.8.188.chello.no> (raw)




Hi,

I recently stumbled over the following problem, recently because the setup
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.

The set-up is as follows:


I got a postgres data base running on a linux machine (the data base works
ok, it seems, as I can connect to it using the psql ``user interface'' to
interact with it).

I want to connect, however, via emacs, in particular, I used
to use the package 

             pg.el (Version: 0.10, 2002, it seems)

for it. Now, part of the proper use of it is establishing the
connection with the data base, which is done by:

(setq myconnection (pg:connect "data-base-name" "user-name") )

Now: this connection does no longer work, i.e., I'm refused
access, giving back the following verdict appended below the end of
the article.

Does anybody know how to repair that?  

I'm not sure where the problem lies (as said, the set-up worked with the same
version of pg.el and basically the same emacs version before). There seem two possible
sources:

  - either emacs/pg does no longer transmit my name properly (I 
      remember I had problems with encodings some time ago)

  - 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.



Thanks, Martin




  signal(error ("Backend error: FATAL:  Ident authentication failed for user \"user-name\"\n"))
  error("Backend error: %s" "FATAL:  Ident authentication failed for user \"msteffen\"\n")

  byte-code("..... process connection pg:SM_USER pg:SM_OPTIONS pg:SM_UNUSED generate-new-buffer " *PostgreSQL*" nil open-network-stream "postgres" fboundp set-buffer-process-coding-system binary set-buffer-multibyte vector cl-struct-pgcon 1 pg:send-int 4 2 pg:send accept-process-output 0 error "pgcon-process accessing a non-pgcon" pg:read-char 69 "Backend error: %s" pg:read-string 4096 82 pg:read-net-int pg:initialize-parsers pg:exec "SET datestyle = 'ISO'" throw --cl-block-pg:connect-- 5 "Crypt authentication not supported" "Kerberos4 authentication not supported" "Kerberos5 authentication not supported" "Can't do that type of authentication: %s" "Problem connecting: expected an authentication response" pg:SM_TTY user-packet-length host port pg:StartupPacketSize pg:PG_PROTOCOL_63_MAJOR ...] 7)

             reply	other threads:[~2006-10-07 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-07 10:14 Martin Steffen [this message]
2006-10-07 11:54 ` failure to connect to postgres DB via pg.el Andreas Seltenreich
2006-10-07 14:55   ` Martin Steffen
     [not found] <mailman.7855.1160216707.9609.help-gnu-emacs@gnu.org>
2006-10-08  2:20 ` Tim X

Reply instructions:

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

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

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m364ewtouv.fsf@cm-84.209.8.188.chello.no \
    --to=msteffen@ifi.uio.no \
    --cc=pgsql-general@postgresql.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).