From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ken Causey <ken@premiernet.net>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Problem with Large Object Interface of pgsql_perl5
Date: Fri, 31 Mar 2000 13:11:18 -0500
Message-ID: <9673.954526278@sss.pgh.pa.us> (raw)
In-Reply-To: <3.0.1.32.20000331101855.016db34c@premiernet.net>
References: <3.0.1.32.20000331101855.016db34c@premiernet.net>
Ken Causey <ken@premiernet.net> writes:
> Can anyone tell me what I'm doing wrong?
Not doing the lo_open inside a transaction. You need begin ... end
around any use of an open large object. (This has always been true,
but older versions of Postgres didn't enforce it --- they'd just die
occasionally if you broke the rule. Now, open LO handles are auto-
closed at transaction commit, which is to say at end of statement
if you're not inside a BEGIN block.)
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, ken@premiernet.net
Subject: Re: Problem with Large Object Interface of pgsql_perl5
In-Reply-To: <9673.954526278@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