Re: Binary large object processing problems - Mailing list pgsql-general

From Raivo Rebane
Subject Re: Binary large object processing problems
Date
Msg-id CAMH5fpvvmFzJvV=QZBB2Ny4zKyNUzj2POswsbXpw+_o7-ecupQ@mail.gmail.com
Whole thread Raw
In response to Re: Binary large object processing problems  (Christoph Moench-Tegeder <cmt@burggraben.net>)
Responses Re: Binary large object processing problems  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thank for answer, but I was also readed this manual and found there :

35.3.2. Importing a Large Object

To import an operating system file as a large object, call

Oid lo_import(PGconn *conn, const char *filename);

filename specifies the operating system name of the file to be imported as a large object. The return value is the OID that was assigned to the new large object, or InvalidOid (zero) on failure. Note that the file is read by the client interface library, not by the server; so it must exist in the client file system and be readable by the client application.

This file what I want to import is readable, I just tested it. So I expected that lo_import doesn't work properly. It answers to my - invalid large-object descriptor: 0
why ?

I try now by creating, opening, writing and closing sequence or are there alternatives ?

Regards
Raivo



On Mon, Mar 13, 2023 at 5:26 PM Christoph Moench-Tegeder <cmt@burggraben.net> wrote:
## Raivo Rebane (raivore55@gmail.com):

> Can anybody help me find where is my mistake an what is working solution ?

The documentation clearly states "All large object manipulation using
these functions must take place within an SQL transaction block"
https://www.postgresql.org/docs/current/lo-interfaces.html
but I couldn't see anything of thank kind in your code.

Regards,
Christoph

--
Spare Space.

pgsql-general by date:

Previous
From: Christoph Moench-Tegeder
Date:
Subject: Re: Binary large object processing problems
Next
From: Tom Lane
Date:
Subject: Re: Binary large object processing problems