From: Donald Carlile <carlile@me.com>
Content-type: text/plain; charset=windows-1252
Content-transfer-encoding: quoted-printable
Subject: PQExec returns null question
Message-id: <D2BB3EEC-5FA7-4EB3-B232-ADBBC06590B0@me.com>
Date: Mon, 20 Oct 2014 09:53:20 -0700
To: pgsql-interfaces@postgresql.org
MIME-version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Precedence: bulk
Sender: pgsql-interfaces-owner@postgresql.org

Our OS X application uses PostgreSQL as a back end through pqlib. Some of o=
ur customers are reporting occasional PGRES_FATAL_ERRORs, but PQresultError=
Message returns a blank string. I have looked at the sources, and as far as=
 I can tell, this condition can only occur when PQExec returns a null. The =
docs say that this shouldn=92t happen except in out of memory conditions. I=
 am not using any Copy actions.

I have two broad questions. 1) What can I do to prevent this from happening=
? 2) If it does happen, how can I remedy it?

I have increased the shared memory, and that seems to have helped somewhat,=
 but it still occurs. In our experience, once this starts happening, it con=
tinues for every subsequent query.  WE have found that restarting the machi=
ne will remedy it for a time, but is there a less drastic action we can tak=
e that will also remedy it? Perhaps stopping and starting PostgreSQL? Or ar=
e system resources being consumed to the level that a system restart is req=
uired?

Many Thanks,
Don Carlile

--=20
Sent via pgsql-interfaces mailing list (pgsql-interfaces@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-interfaces