From: Martin Steffen <msteffen@ifi.uio.no>
To: help-gnu-emacs@gnu.org
Subject: pg.el: pg:connect -> Backend error: FATAL unsupported frontend protocol 1.0: server supports 2.0 to 3.0
Date: Mon, 26 Nov 2018 10:48:27 +0100 [thread overview]
Message-ID: <xk92r2f8tbis.fsf@rijkaard.ifi.uio.no> (raw)
Hi,
I encountered a problem with postgres/pg.el after a recent upgrade of
the OS (fedora/postgres). It well might be that pg.el is not the
``culprit'' but I was not able to properly nail it down and I don't know
how to localize is.
On a very high level, the problem is: connecting to an existing data base
via pg.el yields the message
--------------------------
pg:connect: Backend error: FATAL: unsupported frontend protocol 1.0: server supports 2.0 to 3.0
--------------------------
On the surface, the problem is kind of clear: somewhere/somehow, protocol
1.0 is no longer supported any more-
So far so good, the question is what to do about it (short of trying if one
get's hold of an outdated postgres version, which is a non-options).
What makes it puzzling for me are the following points:
1) I can still access my postgres DB properly. that includes access
``via emacs'' in the sense of using sql-mode (sql.el) and functions like
sql-postgres.
So, there's nothing wrong with the data-base, and some other
emacs-modes are also willing to handle connection to my data
base (but not pg.el)
2) searching around on the internet I found some
discussion/mentioning of the ``unsupported frontend protocol''
phenomenon, but I could not find much information that seemed
helpful for me.
The longest discussion is a blog detailing reasons for the
``unsupported-protocol-mystery'' (as the blog title reads):
https://www.endpoint.com/blog/2015/05/28/postgres-unsupported-frontend-protocol
Unfortunately, I was unable to turn that discussion into
something that helps me to address my problem. Besides (if I
interpret the analysis correct), the problem is poinpointed to
nmap ``bingo, mystery solved. [...] most likely caused by
someone running nmap in version detection mode.'' My machine did
not have nmap running or even installed, so nmap is not the
source of the problem on my machine.
I would he happy about any ideas where to dig (or even where to ask;
perhaps pg.el, is where it manifests itself for me, but it should be
tackled perhaps in some other package or component, but the question
would be where).
Thanks a lot, Martin
PS: for completeness sake: I use the very latest version of pg.el
"0.13+" resp "0.12", both have the same reaction. For emacs I use emacs
26.1)
next reply other threads:[~2018-11-26 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 9:48 Martin Steffen [this message]
2018-11-27 18:23 ` pg.el: pg:connect -> Backend error: FATAL unsupported frontend protocol 1.0: server supports 2.0 to 3.0 Stefan Monnier
2018-11-28 2:48 ` Jean Louis
[not found] ` <mailman.4740.1543343005.1284.help-gnu-emacs@gnu.org>
2018-11-28 5:58 ` martin.sputnik
2018-11-30 15:51 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xk92r2f8tbis.fsf@rijkaard.ifi.uio.no \
--to=msteffen@ifi.uio.no \
--cc=help-gnu-emacs@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.