Re: postgres_fdw has insufficient support for large object - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: postgres_fdw has insufficient support for large object
Date
Msg-id CAKFQuwZjG2d65Aw6bNJ9yEhdTx_y5qazxbiAW+_qNy3NFO-4jA@mail.gmail.com
Whole thread Raw
In response to postgres_fdw has insufficient support for large object  ("Saladin" <jiaoshuntian@highgo.com>)
List pgsql-hackers
On Sunday, May 22, 2022, Saladin <jiaoshuntian@highgo.com> wrote:

The output i expected:
pg_largeobject_metadata and pg_largeobject in both database A and database
B should have rows.Shouldn't only in database A.So, i can use large object
functions
to operate large_objectin remote table or foreign table.

This is an off-topic email for the -hackers mailing list.  -general is the appropriate list.

Your expectation is simply unsupported by anything in the documentation.

If you want to do what you say you will need to use dblink (and the file needs to be accessible to the remote server directly) and directly execute entire queries on the remote server, the FDW infrastructure simply does not work in the way you are expecting.

Or just use bytea.

David J.
 

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns
Next
From: Peter Eisentraut
Date:
Subject: Re: automatically generating node support functions