From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: dblink without running the full query remotely? |
Date: | 2023-08-25 22:12:32 |
Message-ID: | CAOC+FBWRCUKSJr0Y4DgtPwJCJOtEb_FT395dmub=ggKE2YLXiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks, this it exactly.
Correlated, is there a way to define a fdw user mapping for a role versus
for every single individual user in a database?
On Fri, Aug 25, 2023 at 2:16 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Wells Oliver <wells(dot)oliver(at)gmail(dot)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
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | M Sarwar | 2023-08-25 22:26:28 | Re: dblink without running the full query remotely? |
Previous Message | Tom Lane | 2023-08-25 21:16:46 | Re: dblink without running the full query remotely? |