Re: Graceful handling of DB connectivity failures

From: Naresh V <nareshov_at_gmail.com>
Date: Thu, 16 Jun 2011 14:20:02 +0530

On 16 June 2011 02:19, Murray S. Kucherawy <msk_at_cloudmark.com> wrote:
> I reproduced this in a local test setup here.  There appears to be a bug or a limitation with opendbx, wherein a particular kind of error from libpq (the postgresql library) leaves the database handle in an unrecoverable state.  I've posted a note to the opendbx mailing list to describe the problem and ask for help with it.
>
> Some database types we support can handle high-bit characters and others (apparently) can't.  I'm not sure whether we should be fixing this in opendkim or pushing to get the libraries below it fixed.  We could, I suppose, just force a "not found" response to DB queries that include high-bit ASCII if certain flags are set in the configuration file.
>
> In the meantime, you might be able to adjust your postgresql server to tolerate high-ASCII characters which would avoid this problem.  Unfortunately I don't know enough about postgresql to tell you how to do that, but maybe their "client_encoding" hint is useful.
>

Hi Murray,

The client_encoding in my postgres db is UTF-8.
(The client has an option to \set client_encoding <something else>'
before performing the query though)


-Naresh V.
Received on Thu Jun 16 2011 - 08:50:16 PST