Re: Strange Bug in exim4 postgresql lookup code or libpq?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:58:33
Message-ID: 14509.1126799913@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alexander Neumann <alexander(at)bumpern(dot)de> 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?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Peter Alberer 2005-09-15 16:03:42 Re: Problem with 64-bit Postgres
Previous Message Martijn van Oosterhout 2005-09-15 15:53:23 Re: Strange Bug in exim4 postgresql lookup code or libpq?