From: Tom Lane <tgl@sss.pgh.pa.us>
To: Florian Baumert <baumert@plt.de>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Postgresql + lo
Date: Thu, 08 Jul 1999 21:16:14 -0400
Message-ID: <1300.931482974@sss.pgh.pa.us> (raw)
In-Reply-To: <1913.990709@plt.de>
Florian Baumert <baumert@plt.de> writes:
> What happens is that it writes a -1 to the screen and a database-error "ERROR: lo_lseek: invalid large obj descriptor (0)"
This needs to go into the FAQ, I think, 'cause you're about the third
person to ask the same question in the past couple weeks.
You need to wrap a transaction ("begin" ... "commit") around any use
of a large object handle, ie any lo_open ... lo_close sequence.
This requirement has always been in the LO docs, but Postgres 6.5 is the
first release that enforces the rule (by closing all open LO handles at
end of statement, if not within a transaction). In prior versions,
you could sometimes get away with not using a transaction, but it
was NOT reliable.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, baumert@plt.de
Subject: Re: [INTERFACES] Postgresql + lo
In-Reply-To: <1300.931482974@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox