From: Chris Nicholas <cgn@globexplorer.com>
To: pgsql-interfaces@postgreSQL.org
Subject: dynamic large objects <-> C procs; HOWTO?
Date: Tue, 22 Aug 2000 23:19:52 -0700 (PDT)
Message-ID: <200008230619.XAA02372@chis.globexplorer.com> (raw)
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
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: cgn@globexplorer.com
Subject: Re: dynamic large objects <-> C procs; HOWTO?
In-Reply-To: <200008230619.XAA02372@chis.globexplorer.com>
* 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