Received: from chis.globexplorer.com ([208.25.182.139]) by hub.org (8.10.1/8.10.1) with ESMTP id e7N6JwT68573 for ; Wed, 23 Aug 2000 02:19:58 -0400 (EDT) Received: (from cgn@localhost) by chis.globexplorer.com (8.9.3/8.9.3) id XAA02372 for pgsql-interfaces@postgreSQL.org; Tue, 22 Aug 2000 23:19:52 -0700 (PDT) Date: Tue, 22 Aug 2000 23:19:52 -0700 (PDT) From: Chris Nicholas Message-Id: <200008230619.XAA02372@chis.globexplorer.com> To: pgsql-interfaces@postgreSQL.org Subject: dynamic large objects <-> C procs; HOWTO? X-Archive-Number: 200008/144 Greetings - I was wondering what the best manner of transferring large objects to and from user-defined "C" functions through the JDBC or libpq interfaces might be. These objects are mostly transient query results, and shouldn't be stored on the file system; they are really transcoded imagery, audio, etc formatted on the fly to the user's specifications. I've looked a bit at the lo interfaces, and it seems that (appropriately) everything is geared towards commit/rollback within the executor, such that things are allocated in palloc(), or one gets and oid and sticks stuff into the file system. But is there a way for a user-defined process to somehow support a read(2) and/or a write(2) type of interface via the fastpath mechanisms, given the caveat that these things are outside of transactional control? suggestions/comments/flames welcome. Chris Nicholas