From: | Bucks vs Bytes Inc <postgresql(at)bucksvsbytes(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: unsupported frontend protocol |
Date: | 2005-05-26 10:59:43 |
Message-ID: | 4295AC1F.6050502@bucksvsbytes.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Connection logging shows an unvarying pattern: every connection
attempt, regardless of target database or source (PHP or psql), first
uses a wrong protocol and then succeeds on a second attempt, presumably
after falling back:<br>
<br>
LOG: connection received: host=[local]<br>
FATAL: unsupported frontend protocol<br>
LOG: connection received: host=[local]<br>
LOG: connection authorized: user=testuser database=test<br>
<br>
Any thoughts on what could make both clients attempt wrong protocol?<br>
<br>
/usr/lib has the following libpq files:<br>
-rw-r--r-- 1 root root 592784 Jun 24 2004 /usr/lib/libpq.a<br>
lrwxrwxrwx 1 root root 12 Jul 8 2004
/usr/lib/libpq.so -> libpq.so.3.1<br>
lrwxrwxrwx 1 root root 12 Nov 28 2003
/usr/lib/libpq.so.2 -> libpq.so.2.2<br>
-rwxr-xr-x 1 root root 61252 Nov 4 2003
/usr/lib/libpq.so.2.2<br>
lrwxrwxrwx 1 root root 12 Jul 8 2004
/usr/lib/libpq.so.3 -> libpq.so.3.1<br>
-rwxr-xr-x 1 root root 112040 Jun 24 2004
/usr/lib/libpq.so.3.1<br>
<br>
<br>
Tom Lane wrote:
<blockquote cite="mid14750(dot)1117071655(at)sss(dot)pgh(dot)pa(dot)us" type="cite">
<pre wrap="">Bucks vs Bytes Inc <a class="moz-txt-link-rfc2396E" href="mailto:postgresql(at)bucksvsbytes(dot)com"><postgresql(at)bucksvsbytes(dot)com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">Is there any postmaster logging I can turn on that will detail what's
triggering the error?
</pre>
</blockquote>
<pre wrap=""><!---->
Well, you could change the error report in postmaster.c to show the
specific protocol version code it's receiving (7.4 and up do this,
but it hadn't occurred to us as of 7.3). I have little doubt what
you will find though. Maybe what you really want is to enable
log_connections so you can find out where the problematic connections
are coming from.
regards, tom lane
</pre>
</blockquote>
</body>
</html>
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/html | 2.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Himanshu Baweja | 2005-05-26 11:39:52 | Bgwriter--- BufferSync() and StrategyStatsDump() |
Previous Message | Russell Smith | 2005-05-26 08:30:26 | Re: bulk loading of bplus index tree |