Hi, * Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > Alexander Neumann <alexander@xxxxxxxxxx> writes: > > In short terms: The result code is PGRES_FATAL_ERROR, but the error message > > is an empty string. > AFAIK that shouldn't happen, unless perhaps you are completely out of > memory in the client-side process. What shows up in the postmaster > error log when this occurs? =================<snip>======================== 2005-09-01 18:19:01 [5462] LOG: connection received: host=127.0.0.1 port=41446 2005-09-01 18:19:01 [5462] LOG: connection authorized: user=exim database=pfauadmin 2005-09-01 18:19:01 [5462] LOG: statement: SELECT domain || ' : ' FROM exim_virtual_domains 2005-09-01 18:19:01 [5462] LOG: statement: SELECT sa_enable 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: 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 =================<snip>======================== The first query succeeds, the second fails. Both work and deliver exactly the results as expected, when cut&pasted from the logs (either exim or postgresql)... Thanks for reading, - Alexander
Attachment:
pgp9EFZwZAelm.pgp
Description: PGP signature
