Received: from localhost (IDENT:root@hectic-1.jpl.nasa.gov [128.149.68.203]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA74647 for ; Fri, 30 Jul 1999 10:06:37 -0400 (EDT) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (lockhart@localhost [127.0.0.1]) by localhost (8.8.7/8.8.7) with ESMTP id OAA10684; Fri, 30 Jul 1999 14:06:29 GMT Sender: lockhart@hub.org Message-ID: <37A1B165.BF7D6F46@alumni.caltech.edu> Date: Fri, 30 Jul 1999 14:06:29 +0000 From: Thomas Lockhart X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.0.36 i686) X-Accept-Language: en MIME-Version: 1.0 To: John David Garza CC: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] jdbc, pgsql6.5.1, large objects References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Let's see, my admin just upgraded postgresql to 6.5.1 and now it looks > like FastPath isn't working. More specifically, after creating and opening > a large object using the LargeObjectManager class, any other access > attempts throws the following: > Before upgrading to 6.5.1, this program worked fine. Calls to tell, size, > read all cause the same type of exceptions. Put all the accesses to a large object inside a transaction. The restriction was always there in principle, but was not enforced in earlier releases. - Thomas -- Thomas Lockhart lockhart@alumni.caltech.edu South Pasadena, California