Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.2/8.9.1) with ESMTP id LAA37708
	for <pgsql-interfaces@postgreSQL.org>;
	Sat, 17 Apr 1999 11:49:09 -0400 (EDT)
	(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 LAA23610;
	Sat, 17 Apr 1999 11:48:05 -0400 (EDT)
To: Yu Cao <yucao@falcon.kla-tencor.com>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] TBLOCK status from libpq / libpq++ 
In-reply-to: Your message of Fri, 16 Apr 1999 20:03:00 -0700 (PDT)
	<Pine.SOL.3.96.990416195855.19836B-100000@wavelet.kla-tencor.com>
Date: Sat, 17 Apr 1999 11:48:04 -0400
Message-ID: <23608.924364084@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Yu Cao <yucao@falcon.kla-tencor.com> writes:
> Is there a way I can find out whether I'm inside a transaction
> block (between "BEGIN" and "END") by calling some libpq function?

No, libpq has no idea what the backend's status is.  If you need to
know this, I suggest keeping track of it in your own application code.

			regards, tom lane