Received: from hksys.com (IDENT:root@dns.hksys.com [206.222.220.16]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA91574 for ; Fri, 23 Jul 1999 10:26:14 -0400 (EDT) (envelope-from jeremy@hksys.com) Received: from silver (silver.hksys.com [10.0.1.13]) by hksys.com (8.9.3/8.8.7) with SMTP id JAA12023 for ; Fri, 23 Jul 1999 09:25:54 -0500 Message-ID: <003e01bed517$460d3f70$0d01000a@hksys.com> From: "Jeremy Bettis" To: References: <14398.932738250@sss.pgh.pa.us> Subject: Re: [INTERFACES] Postgresql + lo Date: Fri, 23 Jul 1999 09:25:53 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 X-Logged: Logged by hksys.com as JAA12023 at Fri Jul 23 09:25:54 1999 I ran into this same problem. I think some of the source of the confusion is that the perl5 interface documentation do not mention any such restriction. -- Jeremy Bettis jeremy@hksys.com > You need "begin transaction"/"end transaction" around the use of the > LO handle (ie, surrounding lo_open ... lo_close). > > The documentation has always stated that lo_open must be wrapped in > a transaction, but Postgres versions before 6.5 didn't enforce that > rule. (Instead, they'd just fail occasionally if you broke it :-(.)