From: Thomas Lockhart <lockhart@alumni.caltech.edu>
To: John David Garza <garza@cjas.org>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] jdbc, pgsql6.5.1, large objects
Date: Fri, 30 Jul 1999 14:06:29 +0000
Message-ID: <37A1B165.BF7D6F46@alumni.caltech.edu> (raw)
References: <Pine.BSF.4.10.9907292129190.46423-100000@localhost>
> 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
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: lockhart@alumni.caltech.edu, garza@cjas.org
Subject: Re: [INTERFACES] jdbc, pgsql6.5.1, large objects
In-Reply-To: <37A1B165.BF7D6F46@alumni.caltech.edu>
* 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