Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA41581 for ; Fri, 31 Mar 2000 13:11:40 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id NAA09676; Fri, 31 Mar 2000 13:11:18 -0500 (EST) To: Ken Causey cc: pgsql-interfaces@postgresql.org Subject: Re: Problem with Large Object Interface of pgsql_perl5 In-reply-to: <3.0.1.32.20000331101855.016db34c@premiernet.net> References: <3.0.1.32.20000331101855.016db34c@premiernet.net> Comments: In-reply-to Ken Causey message dated "Fri, 31 Mar 2000 10:18:55 -0600" Date: Fri, 31 Mar 2000 13:11:18 -0500 Message-ID: <9673.954526278@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200003/10 Ken Causey 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