Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.1/8.9.1) with ESMTP id LAA17772
	for <pgsql-interfaces@postgreSQL.org>;
	Mon, 26 Oct 1998 11:16:52 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA03792;
	Mon, 26 Oct 1998 11:16:11 -0500 (EST)
To: peter.garner@toward.com
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] large object error 
In-reply-to: Your message of Mon, 26 Oct 1998 01:00:32 EDT
	<199810260100.AA107415366@piglet.toward.com>
Date: Mon, 26 Oct 1998 11:16:11 -0500
Message-ID: <3790.909418571@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Peter  Garner" <peter.garner@toward.com> writes:
> I am getting a wierd error attempting to access the lobs.
> When I close the lob, I get the error 
> PQfn: expected a 'V' from the backend. Got 'N' instead

This is a bug in libpq 6.3.2 (and probably all prior releases).
It doesn't cope with "NOTICE" messages issued by the backend during
a fast-path function call, which is what all the lo_XXX routines are.

It's impossible to guess from this much info what the NOTICE is and
whether it's anything significant; very possibly it's ignorable.
The backend is willing to proceed with the transaction, anyway.

This bug is fixed in the current sources.  Although 6.4 is officially
still beta, I'd really suggest using a current snapshot in place of
6.3.2 --- I believe the current sources are more stable than 6.3.2.
(My company is currently running production apps on a server built
from a late-September snapshot, and it's given us no trouble ...
whereas 6.3.2 had some nasty bugs that got tickled by our apps.)

Alternatively, I think that a small patch to the 6.3.2 sources to handle
NOTICE messages during PQfn() was posted to one or another of the pgsql
mailing lists sometime this summer (not by me).  Check the archives.

			regards, tom lane