From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Alexander Neumann <alexander(at)bumpern(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Strange Bug in exim4 postgresql lookup code or libpq? |
Date: | 2005-09-15 15:52:26 |
Message-ID: | 20050915155226.GB21434@surnet.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Sep 15, 2005 at 03:14:10PM +0200, Alexander Neumann wrote:
> I'm using exim4 together with postgresql. Sometimes, data lookups fail
> mysteriously and on the exim side nobody was able to help.
>
> In short terms: The result code is PGRES_FATAL_ERROR, but the error message
> is an empty string.
>
> I opened up a bug in the exim bugzilla:
> http://www.exim.org/bugzilla/show_bug.cgi?id=45
Notice this part of the Postgres log:
2005-09-01 18:19:01 [5462] LOG: statement: SELECT sa_tempreject_score FROM
exim_virtual_addresses WHERE domain = 'xxxx.org' AND (mailbox = 'xxxxxxxxx' OR
mailbox = '*') ORDER BY mailbox DESC LIMIT 1
2005-09-01 18:19:01 [5462] LOG: unexpected EOF on client connection
Why is the client closing the connection? This seems to be a bug in the
client. Notice that the last query registered for process 5462 is
against table sa_tempreject_score, but your first log snippet shows, on
line 2, a query against table sa_reject_score which is failing. The
first line says something about a tempreject_score, which probably comes
from the last query Postgres received.
The connection cache code needs some looking at, apparently ...
--
Alvaro Herrera -- Valdivia, Chile Architect, www.EnterpriseDB.com
"Hay que recordar que la existencia en el cosmos, y particularmente la
elaboración de civilizaciones dentre de él no son, por desgracia,
nada idílicas" (Ijon Tichy)
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2005-09-15 15:53:23 | Re: Strange Bug in exim4 postgresql lookup code or libpq? |
Previous Message | Janning Vygen | 2005-09-15 15:30:35 | Re: ERROR: type "temp_gc" already exists |