From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: dblink without running the full query remotely?
In-reply-to: 
 <CAOC+FBWCx3iunwdXYRKmr89O2qXNeOHgSTvv13Cju73LNcvKEA@mail.gmail.com>
References: 
 <CAOC+FBWCx3iunwdXYRKmr89O2qXNeOHgSTvv13Cju73LNcvKEA@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Fri, 25 Aug 2023 11:20:23 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4193746.1692998206.1@sss.pgh.pa.us>
Date: Fri, 25 Aug 2023 17:16:46 -0400
Message-ID: <4193747.1692998206@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/4193747.1692998206%40sss.pgh.pa.us>
Precedence: bulk

Wells Oliver <wells.oliver@gmail.com> writes:
> Per the documentation -- *dblink fetches the entire remote query result
> before returning any of it to the local system* -- I am guessing the answer
> is no, but I wondered if there was some way to do something like this:
> ...
> Where that remote sometable might have a bajillion rows and the local where
> would be passed to it

No, and it's unlikely anyone would ever put effort into making dblink
do that, because the newer foreign table (FDW) code *does* handle that
sort of thing.  dblink still has its uses, but it's pretty much at a
dead end developmentally.  Take a look at postgres_fdw.

			regards, tom lane