From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Martin Steffen Newsgroups: gmane.emacs.help 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 Organization: IFI UiO Norway Message-ID: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1543240049 30150 195.159.176.226 (26 Nov 2018 13:47:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 26 Nov 2018 13:47:29 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Nov 26 14:47:24 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gRHEP-0007fx-QI for geh-help-gnu-emacs@m.gmane.org; Mon, 26 Nov 2018 14:47:22 +0100 Original-Received: from localhost ([::1]:36059 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRHGW-0006If-8H for geh-help-gnu-emacs@m.gmane.org; Mon, 26 Nov 2018 08:49:32 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gRDVf-0007gW-3B for help-gnu-emacs@gnu.org; Mon, 26 Nov 2018 04:48:57 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gRDVb-0005jb-OX for help-gnu-emacs@gnu.org; Mon, 26 Nov 2018 04:48:55 -0500 Original-Received: from mail-out01.uio.no ([2001:700:100:10::50]:59464) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gRDVb-0005bP-3o for help-gnu-emacs@gnu.org; Mon, 26 Nov 2018 04:48:51 -0500 Original-Received: from mail-mx12.uio.no ([129.240.10.84]) by mail-out01.uio.no with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gRDVO-00078p-1b for help-gnu-emacs@gnu.org; Mon, 26 Nov 2018 10:48:38 +0100 Original-Received: from rijkaard.ifi.uio.no ([129.240.69.2] helo=rijkaard.ifi.uio.no.shmi.ifi.uio.no) by mail-mx12.uio.no with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from ) id 1gRDVM-000F94-Pf; Mon, 26 Nov 2018 10:48:37 +0100 X-UiO-SPF-Received: Received-SPF: neutral (mail-mx12.uio.no: 129.240.69.2 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.69.2; envelope-from=msteffen@ifi.uio.no; helo=rijkaard.ifi.uio.no.shmi.ifi.uio.no; X-UiO-Spam-info: not spam, SpamAssassin (score=-4.3, required=5.0, autolearn=disabled, SPF_NEUTRAL=0.652, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO) X-UiO-Scanned: 0294035FEFE1007E1496CFE9DFDDC2C74B80285C X-UiOonly: A1B16BB129A9ED062433289E092D8BBCF88D2A8F X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 2001:700:100:10::50 X-Mailman-Approved-At: Mon, 26 Nov 2018 08:48:38 -0500 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:118761 Archived-At: 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)