From: L J Bayuk <ljb220@mindspring.com>
Message-Id: <200402230109.i1N199pP001050@mindspring.com>
Subject: Re: create large object by tcl
To: hehe88hk@yahoo.com.hk (=?big5?q?Wong=20Eric?=)
Date: Sun, 22 Feb 2004 20:09:09 -0500 (EST)
Cc: pgsql-interfaces@postgresql.org
In-Reply-To: <20040222141220.75395.qmail@web14908.mail.yahoo.com> from
	"=?big5?q?Wong=20Eric?=" at Feb 22, 2004 10:12:20 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> However, I would like to ask why a transaction is
> needed for accessing large object?

Here's how I understand it. If I get it badly wrong, perhaps someone
else will step in and correct me.

The PostgreSQL database server creates a context in which to store
information it needs to process commands.  If you don't start a transaction
block with BEGIN, a new context is created for each command, and destroyed
after the command is processed.  If you use BEGIN to start a transaction
block, the context stays around until you use COMMIT or ROLLBACK to end the
transaction block.

Large object file descriptors, like cursors, are stored in this context.
So if you open a large object outside a transaction block, the large object
file descriptor you get back is invalid, because the context it was created
in was already destroyed.