[ Re-post after re-resubscribing. Sorry if this gets through twice. I'd
have sworn on Euclid's "Elements" I was already subscribed ... ]
To mitigate both Patrick's issue and Tom's answer, it should be said
that the current doc is quite light on blob use and issues. Some
pointers to external docs might be welcome ...
(BTW, the same could be said of a lot of non-core stuff (e. g. using
Python as a procedural language, which uses a module alluded to but
having no documentation I could lay my yeyes on ... The "Right Thing" to
do in such an odccurence might be the way the Python client interface
does : it describes the (now obsolete) pypgsql module, but points to the
correct (meta-)reference to DB API 2.0).
Tom Lane wrote:
> Patrick Nelson <pnelson@neatech.com> writes:
>
>>There is \lo_import, \lo_export, \lo_list, and \lo_unlink which seem to
>>utilize a remote client to upload, but this isn't a great solution if your
>>not using psql.
>
>
> If you're not using psql, what are you using?
>
> psql's \lo facilities are just interfaces to a set of libpq routines,
> which you can use for yourself if you're coding in C or C++. If you're
> using some other API that doesn't offer equivalent facilities, meseems
> you have a gripe against that API.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
