Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] jdbc, pgsql6.5.1, large objects

From: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>
To: John David Garza <garza(at)cjas(dot)org>
Cc: pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] jdbc, pgsql6.5.1, large objects
Date: 1999-07-30 14:06:29
Message-ID: 37A1B165.BF7D6F46@alumni.caltech.edu (view raw or flat)
Thread:
Lists: pgsql-interfaces
> 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(at)alumni(dot)caltech(dot)edu
South Pasadena, California

In response to

pgsql-interfaces by date

Next:From: Collin F. LynchDate: 1999-07-30 14:53:49
Subject: libpgtcl.so.2.0
Previous:From: Tom LaneDate: 1999-07-30 13:57:43
Subject: Re: [INTERFACES] jdbc, pgsql6.5.1, large objects

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group